Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a73d159a62cf491506d58dfea93a6606c60ac9f941c8b1c59f200b6590f1e57

Tx prefix hash: 665e8541af75623a3d0087ad9d613183128cca66f82800285729e5a119f7de24
Tx public key: 23cde64baa0def97abb2a6e813a705d3e1c80fa45a4e0023a4129a70475c0e21
Timestamp: 1741515002 Timestamp [UCT]: 2025-03-09 10:10:02 Age [y:d:h:m:s]: 00:257:13:02:13
Block: 1235472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181795 RingCT/type: yes/0
Extra: 0123cde64baa0def97abb2a6e813a705d3e1c80fa45a4e0023a4129a70475c0e21021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b9f891e5e7d22ed085f80ffa5846bbe8d499afa1cf94669ac02e7c99b813fc9 0.600000000000 1722411 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": 1235482, "vin": [ { "gen": { "height": 1235472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b9f891e5e7d22ed085f80ffa5846bbe8d499afa1cf94669ac02e7c99b813fc9" } } ], "extra": [ 1, 35, 205, 230, 75, 170, 13, 239, 151, 171, 178, 166, 232, 19, 167, 5, 211, 225, 200, 15, 164, 90, 78, 0, 35, 164, 18, 154, 112, 71, 92, 14, 33, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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