Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad0d70d1797a5c13d338d43ef1a49a9c158a9cdeca9d39a52fd8216f4da6c2b3

Tx prefix hash: 34fe8ff0ddbd8a1d808e672657f3eb3ee673e60675626e23379c447b23abd423
Tx public key: 5f8a63ab6e11ec7ac5ff26fda7e376444eb672e3cd06563bbef23c414920b614
Timestamp: 1724703880 Timestamp [UCT]: 2024-08-26 20:24:40 Age [y:d:h:m:s]: 00:221:10:42:01
Block: 1096535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158147 RingCT/type: yes/0
Extra: 015f8a63ab6e11ec7ac5ff26fda7e376444eb672e3cd06563bbef23c414920b614021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e22f948f6e238658d0af328759efa0c27c0e2d262875b8f335bf72e275779e47 0.600000000000 1571726 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": 1096545, "vin": [ { "gen": { "height": 1096535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e22f948f6e238658d0af328759efa0c27c0e2d262875b8f335bf72e275779e47" } } ], "extra": [ 1, 95, 138, 99, 171, 110, 17, 236, 122, 197, 255, 38, 253, 167, 227, 118, 68, 78, 182, 114, 227, 205, 6, 86, 59, 190, 242, 60, 65, 73, 32, 182, 20, 2, 17, 0, 0, 0, 2, 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