Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3bedbb66badc34774b5ac7246b903fc3e57b1499f99197b197bd4028df0aba3

Tx prefix hash: 7e5c55ee00f1df3aa5cd8e9c8f3471de97dd196ca9c7935fa49bde7ecfa38fee
Tx public key: 2e4d150450a31096a65aa570ac02e2e936543dd1df3b6003d1f4ae67f32ddf7c
Timestamp: 1626226477 Timestamp [UCT]: 2021-07-14 01:34:37 Age [y:d:h:m:s]: 03:136:09:08:26
Block: 293510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 868553 RingCT/type: yes/0
Extra: 012e4d150450a31096a65aa570ac02e2e936543dd1df3b6003d1f4ae67f32ddf7c02110000001fa272b9cb000000000000000000

1 output(s) for total of 65.386416074000 dcy

stealth address amount amount idx
00: 334cbab35440e5fda97856debd2d426bbca4b7a62d00a276b1b5fcd7233bd2b7 65.386416074000 614932 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": 293520, "vin": [ { "gen": { "height": 293510 } } ], "vout": [ { "amount": 65386416074, "target": { "key": "334cbab35440e5fda97856debd2d426bbca4b7a62d00a276b1b5fcd7233bd2b7" } } ], "extra": [ 1, 46, 77, 21, 4, 80, 163, 16, 150, 166, 90, 165, 112, 172, 2, 226, 233, 54, 84, 61, 209, 223, 59, 96, 3, 209, 244, 174, 103, 243, 45, 223, 124, 2, 17, 0, 0, 0, 31, 162, 114, 185, 203, 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