Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cd80dd7ceb3d1127872219515fd05d38a7dfaf959735bb7bf14e5adba6fc464

Tx prefix hash: a2d7e93a084e3ecaece8f9450295074b4d6b11d64783bfc5004db2772f4627a1
Tx public key: e1f0f7864a49b652072d6fa49d8863f88e7f755388f8176b995cb44fa1c11acd
Timestamp: 1702687328 Timestamp [UCT]: 2023-12-16 00:42:08 Age [y:d:h:m:s]: 01:035:19:53:05
Block: 914017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286932 RingCT/type: yes/0
Extra: 01e1f0f7864a49b652072d6fa49d8863f88e7f755388f8176b995cb44fa1c11acd02110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b47a22aaf93510b1c177d5d2366e779beedec9171dc74c2aa2c7e339faa23e0 0.600000000000 1371297 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": 914027, "vin": [ { "gen": { "height": 914017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b47a22aaf93510b1c177d5d2366e779beedec9171dc74c2aa2c7e339faa23e0" } } ], "extra": [ 1, 225, 240, 247, 134, 74, 73, 182, 82, 7, 45, 111, 164, 157, 136, 99, 248, 142, 127, 117, 83, 136, 248, 23, 107, 153, 92, 180, 79, 161, 193, 26, 205, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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