Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adde4089c8abe1c6d4f1aea337defbdcc91df7fb8174f356b8ce9d7f5e7d6995

Tx prefix hash: 2435a7f58d61ac1cbd2b094f5b74cff2a395ab6f2cf451609d9b3ffd128f32af
Tx public key: 737a35c3cc94f76f62ecb31e15dcbcd190634ad2dda0c483fa93cf7514df93c0
Timestamp: 1734096674 Timestamp [UCT]: 2024-12-13 13:31:14 Age [y:d:h:m:s]: 00:101:20:01:57
Block: 1174338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72544 RingCT/type: yes/0
Extra: 01737a35c3cc94f76f62ecb31e15dcbcd190634ad2dda0c483fa93cf7514df93c0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4cd36d859be6df41b1f9de78eadd0f723f288656ef31f821b2c01b3ce392141 0.600000000000 1660477 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": 1174348, "vin": [ { "gen": { "height": 1174338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4cd36d859be6df41b1f9de78eadd0f723f288656ef31f821b2c01b3ce392141" } } ], "extra": [ 1, 115, 122, 53, 195, 204, 148, 247, 111, 98, 236, 179, 30, 21, 220, 188, 209, 144, 99, 74, 210, 221, 160, 196, 131, 250, 147, 207, 117, 20, 223, 147, 192, 2, 17, 0, 0, 0, 3, 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