Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7d7afaef16f1917877b490f23ea18e9e9809eac25cc38258cbcfdc6ee3d66a9

Tx prefix hash: b31eea2944fb90e5fe4268a3daf1fab20c4d403d314522e7a18c22190d264e35
Tx public key: e51b3cf52d860018872b4df1ae9e618b62d0a3e39df0e50db1a35d318bdc79e0
Timestamp: 1708185308 Timestamp [UCT]: 2024-02-17 15:55:08 Age [y:d:h:m:s]: 00:344:12:23:14
Block: 959606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246381 RingCT/type: yes/0
Extra: 01e51b3cf52d860018872b4df1ae9e618b62d0a3e39df0e50db1a35d318bdc79e002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5077b895c0cbccc56877012955a7f1b1a83f0fc0a158e75bc397490af3e3e4b2 0.600000000000 1419157 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": 959616, "vin": [ { "gen": { "height": 959606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5077b895c0cbccc56877012955a7f1b1a83f0fc0a158e75bc397490af3e3e4b2" } } ], "extra": [ 1, 229, 27, 60, 245, 45, 134, 0, 24, 135, 43, 77, 241, 174, 158, 97, 139, 98, 208, 163, 227, 157, 240, 229, 13, 177, 163, 93, 49, 139, 220, 121, 224, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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