Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 384bdcb64e35127eb0adf264a01e345cd7436e313f090998b069133974ee95f7

Tx prefix hash: 378ac6b68d5239b18979dd08057753f0304729640cbeaaaf2712f243f1f25e58
Tx public key: a75f3c8c07af34fe64b5a34c2d71048cebf2b63b39b3fc9f9c713f6c46791de7
Timestamp: 1588733978 Timestamp [UCT]: 2020-05-06 02:59:38 Age [y:d:h:m:s]: 04:278:17:57:56
Block: 98683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115648 RingCT/type: yes/0
Extra: 01a75f3c8c07af34fe64b5a34c2d71048cebf2b63b39b3fc9f9c713f6c46791de702110000001a86362411000000000000000000

1 output(s) for total of 289.083310555000 dcy

stealth address amount amount idx
00: 69d1bd42a25b7ae62e6e7d34cd37346a694d355c8b8c61b387b509e3e2c45e2b 289.083310555000 174409 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": 98693, "vin": [ { "gen": { "height": 98683 } } ], "vout": [ { "amount": 289083310555, "target": { "key": "69d1bd42a25b7ae62e6e7d34cd37346a694d355c8b8c61b387b509e3e2c45e2b" } } ], "extra": [ 1, 167, 95, 60, 140, 7, 175, 52, 254, 100, 181, 163, 76, 45, 113, 4, 140, 235, 242, 182, 59, 57, 179, 252, 159, 156, 113, 63, 108, 70, 121, 29, 231, 2, 17, 0, 0, 0, 26, 134, 54, 36, 17, 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