Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3d07b99d320b64a901fd6202e8102347e259c6e66a34b080e2556d53f9f9d55

Tx prefix hash: ea822672464e67fb3ab3842c9aa53b3727d6334ecbafb89e3cfce2e565a3bda6
Tx public key: d75466e98364203c3a6996fb5af830469cd2ac8b81a6897316600ef25926c382
Timestamp: 1701579309 Timestamp [UCT]: 2023-12-03 04:55:09 Age [y:d:h:m:s]: 01:131:19:48:40
Block: 904827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355375 RingCT/type: yes/0
Extra: 01d75466e98364203c3a6996fb5af830469cd2ac8b81a6897316600ef25926c382021100000001e08532b6000000000000000000

1 output(s) for total of 0.616499195000 dcy

stealth address amount amount idx
00: e5428a955179a31aa0216b4dace2e6490991b93fcfa44a9b335a4a0ee3ed4b2d 0.616499195000 1361604 of 0

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": 904837, "vin": [ { "gen": { "height": 904827 } } ], "vout": [ { "amount": 616499195, "target": { "key": "e5428a955179a31aa0216b4dace2e6490991b93fcfa44a9b335a4a0ee3ed4b2d" } } ], "extra": [ 1, 215, 84, 102, 233, 131, 100, 32, 60, 58, 105, 150, 251, 90, 248, 48, 70, 156, 210, 172, 139, 129, 166, 137, 115, 22, 96, 14, 242, 89, 38, 195, 130, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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