Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 01fa5e9bad055700f3a660fcfcacd22fc6f9391975b859a2d4f0e0ab10c9a0ca

Tx prefix hash: 45d6dc120786c35a5c611862fafb240aa24e4fa79b4e02d00d9936d3ffb00ef6
Tx public key: ab98c93133b34e34e9f4de2a37a16d9c38ae4d97792470241cb9ecb856198afd
Timestamp: 1722665228 Timestamp [UCT]: 2024-08-03 06:07:08 Age [y:d:h:m:s]: 01:095:23:00:38
Block: 1079653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327058 RingCT/type: yes/0
Extra: 01ab98c93133b34e34e9f4de2a37a16d9c38ae4d97792470241cb9ecb856198afd02110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5811d57437b675bfdfce44501a76942d9e7a0cdf7e145decfc59a556114181ce 0.600000000000 1552702 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1079663, "vin": [ { "gen": { "height": 1079653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5811d57437b675bfdfce44501a76942d9e7a0cdf7e145decfc59a556114181ce" } } ], "extra": [ 1, 171, 152, 201, 49, 51, 179, 78, 52, 233, 244, 222, 42, 55, 161, 109, 156, 56, 174, 77, 151, 121, 36, 112, 36, 28, 185, 236, 184, 86, 25, 138, 253, 2, 17, 0, 0, 0, 17, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8