Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eceefaac410147163a648d4c4e363a1d57722bdf6934468e6f06be505a5abb8

Tx prefix hash: c8a8f65297146ce975c4665e8d9f280e01118011c2caf3bdf74c735b3c86f1e6
Tx public key: fcee37d72c0b2569187de6778c32fc12653537ed6fb166d2c9a503a34f4c0c4d
Timestamp: 1664503664 Timestamp [UCT]: 2022-09-30 02:07:44 Age [y:d:h:m:s]: 02:200:03:47:12
Block: 598595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 664638 RingCT/type: yes/0
Extra: 01fcee37d72c0b2569187de6778c32fc12653537ed6fb166d2c9a503a34f4c0c4d02110000000375e3f0e9000000000000000000

1 output(s) for total of 6.376962010000 dcy

stealth address amount amount idx
00: 2980521af428a7f22e2c4445d13c4372fd0288ccae25fa0dd9686015e6838bdc 6.376962010000 1034374 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": 598605, "vin": [ { "gen": { "height": 598595 } } ], "vout": [ { "amount": 6376962010, "target": { "key": "2980521af428a7f22e2c4445d13c4372fd0288ccae25fa0dd9686015e6838bdc" } } ], "extra": [ 1, 252, 238, 55, 215, 44, 11, 37, 105, 24, 125, 230, 119, 140, 50, 252, 18, 101, 53, 55, 237, 111, 177, 102, 210, 201, 165, 3, 163, 79, 76, 12, 77, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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