Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42422f71e58ce868edd4c9b235b2e7bd52f26fec04117cc81b4c0b30cfb33c1a

Tx prefix hash: edc5404ce320ce64ae5d90d52f9b075c10057b61179230dcb9b2a698b54ddfff
Tx public key: 6885a22cb445a05821ab64c6981ebf78b6a021ad7c6de76f47f465e8ddde67bb
Timestamp: 1577905936 Timestamp [UCT]: 2020-01-01 19:12:16 Age [y:d:h:m:s]: 05:132:08:22:50
Block: 36543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244495 RingCT/type: yes/0
Extra: 016885a22cb445a05821ab64c6981ebf78b6a021ad7c6de76f47f465e8ddde67bb02110000002b8a2ee0d9000000000000000000

1 output(s) for total of 464.428351665000 dcy

stealth address amount amount idx
00: 2ffa1bfb65500295407a2018e13fd733a0270fd4dd8124370a354ce7094873ff 464.428351665000 61934 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": 36553, "vin": [ { "gen": { "height": 36543 } } ], "vout": [ { "amount": 464428351665, "target": { "key": "2ffa1bfb65500295407a2018e13fd733a0270fd4dd8124370a354ce7094873ff" } } ], "extra": [ 1, 104, 133, 162, 44, 180, 69, 160, 88, 33, 171, 100, 198, 152, 30, 191, 120, 182, 160, 33, 173, 124, 109, 231, 111, 71, 244, 101, 232, 221, 222, 103, 187, 2, 17, 0, 0, 0, 43, 138, 46, 224, 217, 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