Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be481b2e6411f1e96ee161fa559a75fdd373e07907dc5036b0cf83fdc36a5ec3

Tx prefix hash: 9d9670f51f734bbc7612f2fc0b6b9dc64001d0f1c6cb8ba78d53d2860d87356e
Tx public key: 4001e881076a1658b053faae0056e8e969c413eb368ad005fdf2d1bc09d00d5f
Timestamp: 1731913543 Timestamp [UCT]: 2024-11-18 07:05:43 Age [y:d:h:m:s]: 00:166:07:24:12
Block: 1156232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118695 RingCT/type: yes/0
Extra: 014001e881076a1658b053faae0056e8e969c413eb368ad005fdf2d1bc09d00d5f021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9156b66aa4981d147e9261f4ccece085013f3d9ea9010eae302cebdc4850e592 0.600000000000 1641855 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": 1156242, "vin": [ { "gen": { "height": 1156232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9156b66aa4981d147e9261f4ccece085013f3d9ea9010eae302cebdc4850e592" } } ], "extra": [ 1, 64, 1, 232, 129, 7, 106, 22, 88, 176, 83, 250, 174, 0, 86, 232, 233, 105, 196, 19, 235, 54, 138, 208, 5, 253, 242, 209, 188, 9, 208, 13, 95, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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