Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 849944c4c6c395e2c8b08ec45915974f364924a6852839ac5a59eaa9ebe609ca

Tx prefix hash: ec1022be61699b86ce95f0a5c28062b2fe9b30444df57a3a61f8074275da405b
Tx public key: 573457a7741e4a1aabdc31d7b8f8bedb08a41446bcf1271fda9caf98d6d9fde3
Timestamp: 1730939909 Timestamp [UCT]: 2024-11-07 00:38:29 Age [y:d:h:m:s]: 00:154:15:05:53
Block: 1148164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110349 RingCT/type: yes/0
Extra: 01573457a7741e4a1aabdc31d7b8f8bedb08a41446bcf1271fda9caf98d6d9fde302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcaa0fd84abe4417c63b65278e1a1facd3584f2effca06951f2097aba1326ed9 0.600000000000 1632949 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": 1148174, "vin": [ { "gen": { "height": 1148164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcaa0fd84abe4417c63b65278e1a1facd3584f2effca06951f2097aba1326ed9" } } ], "extra": [ 1, 87, 52, 87, 167, 116, 30, 74, 26, 171, 220, 49, 215, 184, 248, 190, 219, 8, 164, 20, 70, 188, 241, 39, 31, 218, 156, 175, 152, 214, 217, 253, 227, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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