Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3c7eeb0cdad99f06dc958ea93e4261017ef74b84822ea8c69d0a461a4c2acf0

Tx prefix hash: 2d94d26de030c4de963ffd8560be70ad18af9a43952c36ec71ddb463d1efc3f7
Tx public key: fdfb922857906ced5d3fe931fea312a64441857802e51b5345afcaf61deb0c86
Timestamp: 1720908735 Timestamp [UCT]: 2024-07-13 22:12:15 Age [y:d:h:m:s]: 01:116:03:31:14
Block: 1065095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341507 RingCT/type: yes/0
Extra: 01fdfb922857906ced5d3fe931fea312a64441857802e51b5345afcaf61deb0c8602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 726c1cc208ea22314b2fb3bec97efefb35ad78156fc3f2db63b6b9b35e1d3e6c 0.600000000000 1535638 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": 1065105, "vin": [ { "gen": { "height": 1065095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "726c1cc208ea22314b2fb3bec97efefb35ad78156fc3f2db63b6b9b35e1d3e6c" } } ], "extra": [ 1, 253, 251, 146, 40, 87, 144, 108, 237, 93, 63, 233, 49, 254, 163, 18, 166, 68, 65, 133, 120, 2, 229, 27, 83, 69, 175, 202, 246, 29, 235, 12, 134, 2, 17, 0, 0, 0, 6, 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