Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c87cac371da49f2e6b5be489ce731a0b96f0d854eecae501a7909c7124d9ce55

Tx prefix hash: 15238baac50b6b080d7611408f335b6e93818d7908e7cdeeda62effaa443a6cb
Tx public key: 19a14d87ab55fe8d4e747ac2e6bc2bda04cedcfbe00ffd536ea3e5fa90c5cd78
Timestamp: 1578930121 Timestamp [UCT]: 2020-01-13 15:42:01 Age [y:d:h:m:s]: 04:318:10:23:07
Block: 44772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117036 RingCT/type: yes/0
Extra: 0119a14d87ab55fe8d4e747ac2e6bc2bda04cedcfbe00ffd536ea3e5fa90c5cd7802110000009dff58ae94000000000000000000

1 output(s) for total of 436.174343943000 dcy

stealth address amount amount idx
00: b8f18358602270e5e8a708ed18d3f1894377f2d97372609bf675e7ca80a9e30b 436.174343943000 81557 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": 44782, "vin": [ { "gen": { "height": 44772 } } ], "vout": [ { "amount": 436174343943, "target": { "key": "b8f18358602270e5e8a708ed18d3f1894377f2d97372609bf675e7ca80a9e30b" } } ], "extra": [ 1, 25, 161, 77, 135, 171, 85, 254, 141, 78, 116, 122, 194, 230, 188, 43, 218, 4, 206, 220, 251, 224, 15, 253, 83, 110, 163, 229, 250, 144, 197, 205, 120, 2, 17, 0, 0, 0, 157, 255, 88, 174, 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