Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 410fc1eec12489f531d8e631a416bf3f06e8583cb136c4c365eb8076917420c1

Tx prefix hash: e9fe2ba8c6b00c540f03fe9d7e8ee777aad50fec275374d04d4740a85e1ba59c
Tx public key: fb26c65f2f5e440cb95deaec938ad653ece8aa9c4abe2eb48b405ed25af08f3b
Timestamp: 1739259830 Timestamp [UCT]: 2025-02-11 07:43:50 Age [y:d:h:m:s]: 00:328:18:43:18
Block: 1216791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232802 RingCT/type: yes/0
Extra: 01fb26c65f2f5e440cb95deaec938ad653ece8aa9c4abe2eb48b405ed25af08f3b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e4206053cf70cc8e57238c31f3a0d1d7074b069876e38a9c3e20bca88680549 0.600000000000 1703598 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": 1216801, "vin": [ { "gen": { "height": 1216791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e4206053cf70cc8e57238c31f3a0d1d7074b069876e38a9c3e20bca88680549" } } ], "extra": [ 1, 251, 38, 198, 95, 47, 94, 68, 12, 185, 93, 234, 236, 147, 138, 214, 83, 236, 232, 170, 156, 74, 190, 46, 180, 139, 64, 94, 210, 90, 240, 143, 59, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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