Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6ced2dd596b35b3418db7130a540b60515c134a38809db7d48b420d5b4e69c0

Tx prefix hash: f86e48e7a5cf96d32bdc6c5e5ed71dc9c3d0f3e38a18ea7b0a7a53b1beffb161
Tx public key: 1c49408d85100c51d1e75b64b61f962a5bd24f8946210c847292eec29281dc12
Timestamp: 1761960460 Timestamp [UCT]: 2025-11-01 01:27:40 Age [y:d:h:m:s]: 00:009:21:54:58
Block: 1402314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7089 RingCT/type: yes/0
Extra: 011c49408d85100c51d1e75b64b61f962a5bd24f8946210c847292eec29281dc120211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b2f0f61556c8991752a71ae1210228fca8c3dd248d30392ab01ff510ffa470d 0.600000000000 1890633 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": 1402324, "vin": [ { "gen": { "height": 1402314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b2f0f61556c8991752a71ae1210228fca8c3dd248d30392ab01ff510ffa470d" } } ], "extra": [ 1, 28, 73, 64, 141, 133, 16, 12, 81, 209, 231, 91, 100, 182, 31, 150, 42, 91, 210, 79, 137, 70, 33, 12, 132, 114, 146, 238, 194, 146, 129, 220, 18, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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