Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a464625f04f6c66fb10d671a67e64d35b93482cc984f288dc81c210e7dae0c6f

Tx prefix hash: 303a37541ca1536be499d6dbd60ff0a32883047505403aacee1b16f88f67bd1e
Tx public key: 156fcbb6756dd1c8057f5bfddc335aa083408e4bcc93e81d41fac0d87f4e1a8c
Timestamp: 1745544597 Timestamp [UCT]: 2025-04-25 01:29:57 Age [y:d:h:m:s]: 00:020:07:54:30
Block: 1268820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14540 RingCT/type: yes/0
Extra: 01156fcbb6756dd1c8057f5bfddc335aa083408e4bcc93e81d41fac0d87f4e1a8c021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c51233d3a3eaec597aa91c444f3406cbd00068337e9f83ae04634bed166fed35 0.600000000000 1756053 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": 1268830, "vin": [ { "gen": { "height": 1268820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c51233d3a3eaec597aa91c444f3406cbd00068337e9f83ae04634bed166fed35" } } ], "extra": [ 1, 21, 111, 203, 182, 117, 109, 209, 200, 5, 127, 91, 253, 220, 51, 90, 160, 131, 64, 142, 75, 204, 147, 232, 29, 65, 250, 192, 216, 127, 78, 26, 140, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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