Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 962927e767ee27fb72153a75b763e009eeb6385768b4a7f4561b9c01ba7dcbc2

Tx prefix hash: c9b713e60c99c1f46dcb1b43ab6cab5853c0964fcc9b2ad9d3dcdfa875d98cf6
Tx public key: 83f66e54835244585013ec806b53f6d37a79cc42d529197f8d732da5ccf23894
Timestamp: 1745450411 Timestamp [UCT]: 2025-04-23 23:20:11 Age [y:d:h:m:s]: 00:211:02:12:11
Block: 1268033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148583 RingCT/type: yes/0
Extra: 0183f66e54835244585013ec806b53f6d37a79cc42d529197f8d732da5ccf2389402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecfb847c5cbc17e0da79d380599784ed60f682054f86ddde7d20f55cb3027ac2 0.600000000000 1755262 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": 1268043, "vin": [ { "gen": { "height": 1268033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecfb847c5cbc17e0da79d380599784ed60f682054f86ddde7d20f55cb3027ac2" } } ], "extra": [ 1, 131, 246, 110, 84, 131, 82, 68, 88, 80, 19, 236, 128, 107, 83, 246, 211, 122, 121, 204, 66, 213, 41, 25, 127, 141, 115, 45, 165, 204, 242, 56, 148, 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