Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a611a7e2ed2acd0203ad52781992c3d2ce6e1cbf49819f136535fad8d50c8dfd

Tx prefix hash: cdfbac68bb95d95da64bb195b2139a8fe34d369ee0266f5d3770a88dfa61833a
Tx public key: 438620cf8d86a813ffe7049a6d7fd98ea840ae72fa5657406eb7a38c928071f8
Timestamp: 1708120171 Timestamp [UCT]: 2024-02-16 21:49:31 Age [y:d:h:m:s]: 01:052:05:53:05
Block: 959061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298375 RingCT/type: yes/0
Extra: 01438620cf8d86a813ffe7049a6d7fd98ea840ae72fa5657406eb7a38c928071f80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ef62c7cfa905abc2891e2a12061e78611e717948fcf4663d5fb7cc45cc2dd73 0.600000000000 1418590 of 15

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": 959071, "vin": [ { "gen": { "height": 959061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ef62c7cfa905abc2891e2a12061e78611e717948fcf4663d5fb7cc45cc2dd73" } } ], "extra": [ 1, 67, 134, 32, 207, 141, 134, 168, 19, 255, 231, 4, 154, 109, 127, 217, 142, 168, 64, 174, 114, 250, 86, 87, 64, 110, 183, 163, 140, 146, 128, 113, 248, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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