Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f041513094e9630fbbb0b3ffc7545ef349a42a00d76a3db6e5d4871852f769a

Tx prefix hash: 56163e7785188d90fb0af8b03b57cf712ce3845fe84c2cb3ef987e24ad04bced
Tx public key: 3f144979e22dd1f588e19f2cc46c534156a0b6e6710b5e960c89153fb56fd4c4
Timestamp: 1715076192 Timestamp [UCT]: 2024-05-07 10:03:12 Age [y:d:h:m:s]: 01:007:09:13:06
Block: 1016738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266211 RingCT/type: yes/0
Extra: 013f144979e22dd1f588e19f2cc46c534156a0b6e6710b5e960c89153fb56fd4c40211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbdf530f9eef8cc1c88d0e4d6bea476f332bf08be498045d7bd5ecca6c1cff45 0.600000000000 1480407 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": 1016748, "vin": [ { "gen": { "height": 1016738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbdf530f9eef8cc1c88d0e4d6bea476f332bf08be498045d7bd5ecca6c1cff45" } } ], "extra": [ 1, 63, 20, 73, 121, 226, 45, 209, 245, 136, 225, 159, 44, 196, 108, 83, 65, 86, 160, 182, 230, 113, 11, 94, 150, 12, 137, 21, 63, 181, 111, 212, 196, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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