Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5766533873e660dda845a3ee2466ee324ba43f7a1f127ad23acb01a40063daa

Tx prefix hash: f9f1e8e655b3e59e760b8c23677d7282b0c0581c47889a16f5d6a2b0c46db775
Tx public key: d8ae6894e61491070eaeb7097d4306fb8988da930e9729bbfbdce4fddcb44ff8
Timestamp: 1702618684 Timestamp [UCT]: 2023-12-15 05:38:04 Age [y:d:h:m:s]: 01:115:08:00:40
Block: 913452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343560 RingCT/type: yes/0
Extra: 01d8ae6894e61491070eaeb7097d4306fb8988da930e9729bbfbdce4fddcb44ff802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8b7639edc3369b4cc543dc6c7ccc77f8dd22c3af3af47c8f05e15dbdf361927 0.600000000000 1370720 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": 913462, "vin": [ { "gen": { "height": 913452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8b7639edc3369b4cc543dc6c7ccc77f8dd22c3af3af47c8f05e15dbdf361927" } } ], "extra": [ 1, 216, 174, 104, 148, 230, 20, 145, 7, 14, 174, 183, 9, 125, 67, 6, 251, 137, 136, 218, 147, 14, 151, 41, 187, 251, 220, 228, 253, 220, 180, 79, 248, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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