Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcaf5ab3db613f6ad26fd4fe1b49036e6bfa72d36fcc1aa045a48b9b12145f44

Tx prefix hash: c77e2bfb8a746f5d63e717c11abe43b5c3114d4d3f65f4c0c269fb8dc9f45a3f
Tx public key: e256a1f3faec532db8d02005b6ebe558c1c2d666b2a1fdb65d914ed6b7e60747
Timestamp: 1762511118 Timestamp [UCT]: 2025-11-07 10:25:18 Age [y:d:h:m:s]: 00:019:05:52:03
Block: 1406866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13789 RingCT/type: yes/0
Extra: 01e256a1f3faec532db8d02005b6ebe558c1c2d666b2a1fdb65d914ed6b7e60747021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39a8778c170d3fe9ed8834b41da75b961af2e4c4cba7bf2c2fff0e103fa3d0a5 0.600000000000 1895255 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": 1406876, "vin": [ { "gen": { "height": 1406866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39a8778c170d3fe9ed8834b41da75b961af2e4c4cba7bf2c2fff0e103fa3d0a5" } } ], "extra": [ 1, 226, 86, 161, 243, 250, 236, 83, 45, 184, 208, 32, 5, 182, 235, 229, 88, 193, 194, 214, 102, 178, 161, 253, 182, 93, 145, 78, 214, 183, 230, 7, 71, 2, 17, 0, 0, 0, 1, 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