Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ec2e0f19ecb01815d8a7954f8373304174d85df10f215289ce560bcea529c58

Tx prefix hash: a0763bbb8d769c7a37de20d218e4ab98c596c3b66cfa3ba95cec0bb8db7d1c3a
Tx public key: b8e5f00c86c56a3e8aa2f30ac9464b573a7a15a6b16f6a28669229e14e2fca06
Timestamp: 1742995375 Timestamp [UCT]: 2025-03-26 13:22:55 Age [y:d:h:m:s]: 00:217:07:14:14
Block: 1247706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153036 RingCT/type: yes/0
Extra: 01b8e5f00c86c56a3e8aa2f30ac9464b573a7a15a6b16f6a28669229e14e2fca06021100000001d2e40efd000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e15672837433ae995a89e9b73b759b7aae49908e7dc7cf7aa2bfc0cf642b1e42 0.600000000000 1734733 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": 1247716, "vin": [ { "gen": { "height": 1247706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e15672837433ae995a89e9b73b759b7aae49908e7dc7cf7aa2bfc0cf642b1e42" } } ], "extra": [ 1, 184, 229, 240, 12, 134, 197, 106, 62, 138, 162, 243, 10, 201, 70, 75, 87, 58, 122, 21, 166, 177, 111, 106, 40, 102, 146, 41, 225, 78, 47, 202, 6, 2, 17, 0, 0, 0, 1, 210, 228, 14, 253, 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