Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45aa527ba5e26665a2a4293fa68f5323a64dd70da5974f40d75f2365d654dd96

Tx prefix hash: c4593d308119d57e2961f98dd7b4a0486ef5840f4c44b7d43eb5dbe9dcf2adac
Tx public key: d969e9b10f91db46a6ecb16dc4e5a74faa0cb735a246690d22d815b310970a05
Timestamp: 1705117626 Timestamp [UCT]: 2024-01-13 03:47:06 Age [y:d:h:m:s]: 01:043:11:13:51
Block: 934149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292142 RingCT/type: yes/0
Extra: 01d969e9b10f91db46a6ecb16dc4e5a74faa0cb735a246690d22d815b310970a0502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab5f984316c4826e34ebb9f8ffc649f610ed2e7a85ecdfc3c3f72c1df650760d 0.600000000000 1392137 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": 934159, "vin": [ { "gen": { "height": 934149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab5f984316c4826e34ebb9f8ffc649f610ed2e7a85ecdfc3c3f72c1df650760d" } } ], "extra": [ 1, 217, 105, 233, 177, 15, 145, 219, 70, 166, 236, 177, 109, 196, 229, 167, 79, 170, 12, 183, 53, 162, 70, 105, 13, 34, 216, 21, 179, 16, 151, 10, 5, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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