Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45aff43472f07c2c3111163bd01d1d9d012c7a5f6de88bc6c996c29d01e14b87

Tx prefix hash: 3c74e47b8ec9fc17b39c08d7e9f1edcbebbe326a6295c47a841b0f292f4cc566
Tx public key: bdc0717511c4f8b6c448a8ecb91f3cddf6e356cdb52ba339993c23e99e89a5e5
Timestamp: 1583238751 Timestamp [UCT]: 2020-03-03 12:32:31 Age [y:d:h:m:s]: 05:245:09:45:55
Block: 75636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1327997 RingCT/type: yes/0
Extra: 01bdc0717511c4f8b6c448a8ecb91f3cddf6e356cdb52ba339993c23e99e89a5e5021100000130026b59f3000000000000000000

1 output(s) for total of 344.657180054000 dcy

stealth address amount amount idx
00: b3d1ec3bde28c834e75ca23b1cd942b6c2a1ebfba864d9ac975a4d5bf92d9b43 344.657180054000 139592 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": 75646, "vin": [ { "gen": { "height": 75636 } } ], "vout": [ { "amount": 344657180054, "target": { "key": "b3d1ec3bde28c834e75ca23b1cd942b6c2a1ebfba864d9ac975a4d5bf92d9b43" } } ], "extra": [ 1, 189, 192, 113, 117, 17, 196, 248, 182, 196, 72, 168, 236, 185, 31, 60, 221, 246, 227, 86, 205, 181, 43, 163, 57, 153, 60, 35, 233, 158, 137, 165, 229, 2, 17, 0, 0, 1, 48, 2, 107, 89, 243, 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