Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7194f08069f7fb40990d45264d930a06fee254beb12dff8199314871d67ca17c

Tx prefix hash: 4ca4ebdeae003c4c5b08f330cda1382932a36c4f5fc2e5ab194d7a13f327ef72
Tx public key: 11c9b5e2b5c233e88d7b40d67cadbbc031a3ad1aacb1ee01ab56dd57d91e7a2b
Timestamp: 1751941035 Timestamp [UCT]: 2025-07-08 02:17:15 Age [y:d:h:m:s]: 00:184:13:34:09
Block: 1321006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130419 RingCT/type: yes/0
Extra: 0111c9b5e2b5c233e88d7b40d67cadbbc031a3ad1aacb1ee01ab56dd57d91e7a2b021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3f9c4eef03d1f08bca430783d70812dbd05343f75de9c9590d66d938b2bf120 0.600000000000 1808709 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": 1321016, "vin": [ { "gen": { "height": 1321006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3f9c4eef03d1f08bca430783d70812dbd05343f75de9c9590d66d938b2bf120" } } ], "extra": [ 1, 17, 201, 181, 226, 181, 194, 51, 232, 141, 123, 64, 214, 124, 173, 187, 192, 49, 163, 173, 26, 172, 177, 238, 1, 171, 86, 221, 87, 217, 30, 122, 43, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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