Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6e3a4185b647fba67e18e22c189cd36be6c2f3a77324c9fd901a5da91f10bcb

Tx prefix hash: 7491843c1deffef5c084a69aaae4201f012b6533da40378b88e59ab83896f7dc
Tx public key: aa0068f65473391930087d0e264c780d9f56f7db60a1e899dc3e1d7b840265b6
Timestamp: 1727738367 Timestamp [UCT]: 2024-09-30 23:19:27 Age [y:d:h:m:s]: 00:113:19:49:09
Block: 1121713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81335 RingCT/type: yes/0
Extra: 01aa0068f65473391930087d0e264c780d9f56f7db60a1e899dc3e1d7b840265b6021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0ff65a1b92678f51cfc0b4bb079b41fe114bd39a590ad851b6f5708fc08be8f 0.600000000000 1604034 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": 1121723, "vin": [ { "gen": { "height": 1121713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0ff65a1b92678f51cfc0b4bb079b41fe114bd39a590ad851b6f5708fc08be8f" } } ], "extra": [ 1, 170, 0, 104, 246, 84, 115, 57, 25, 48, 8, 125, 14, 38, 76, 120, 13, 159, 86, 247, 219, 96, 161, 232, 153, 220, 62, 29, 123, 132, 2, 101, 182, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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