Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 406499c4e52f725af950f46c80572bf02b44c40a77c765a7b146bd9fdf3acff7

Tx prefix hash: 63c265c78f86c8a931986b59fe730717608a97ddf4d7cbfcece270280fd4ecd2
Tx public key: 4a4d21b110dc3e65149cd6fc417ad5df57f3d0e4ea2ec21de89e3913a82bb560
Timestamp: 1702535848 Timestamp [UCT]: 2023-12-14 06:37:28 Age [y:d:h:m:s]: 01:146:14:38:59
Block: 912769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365926 RingCT/type: yes/0
Extra: 014a4d21b110dc3e65149cd6fc417ad5df57f3d0e4ea2ec21de89e3913a82bb56002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4050951912914fb84b5f3f24523008c88b0cd096b4cc53064a018bcae42211c 0.600000000000 1370005 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": 912779, "vin": [ { "gen": { "height": 912769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4050951912914fb84b5f3f24523008c88b0cd096b4cc53064a018bcae42211c" } } ], "extra": [ 1, 74, 77, 33, 177, 16, 220, 62, 101, 20, 156, 214, 252, 65, 122, 213, 223, 87, 243, 208, 228, 234, 46, 194, 29, 232, 158, 57, 19, 168, 43, 181, 96, 2, 17, 0, 0, 0, 1, 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