Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd880d12c19fff5ce80d16c11cc278f526a609ea674b3d67e2f4955dc24a9513

Tx prefix hash: 002b50139291c400e908631230d678d6ed941bf7024284d2634525bf6c828448
Tx public key: dd2dcfb7dc437a4d073e3164b6d9f7e8ddc92954abd4f4f90f38b1620d461428
Timestamp: 1720544952 Timestamp [UCT]: 2024-07-09 17:09:12 Age [y:d:h:m:s]: 01:123:10:52:56
Block: 1062081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346747 RingCT/type: yes/0
Extra: 01dd2dcfb7dc437a4d073e3164b6d9f7e8ddc92954abd4f4f90f38b1620d461428021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3300b9088e211d941cbb245c36c59394d735500bbbec341d29365279b574ff7d 0.600000000000 1532582 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": 1062091, "vin": [ { "gen": { "height": 1062081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3300b9088e211d941cbb245c36c59394d735500bbbec341d29365279b574ff7d" } } ], "extra": [ 1, 221, 45, 207, 183, 220, 67, 122, 77, 7, 62, 49, 100, 182, 217, 247, 232, 221, 201, 41, 84, 171, 212, 244, 249, 15, 56, 177, 98, 13, 70, 20, 40, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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