Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 043c3c2841fcba38bdab353993a3963a854c3ecb635e0925931edce2b00d3ede

Tx prefix hash: 6e6e5e7382ef14572ee4acfda56b33d4c81f0a5e2f8a4b928993a8390be5b249
Tx public key: 4d2ed613436171ce3694a48ff83c04eef63496ee23e5eb7ecb1850b27eb1bc3e
Timestamp: 1700849888 Timestamp [UCT]: 2023-11-24 18:18:08 Age [y:d:h:m:s]: 01:097:04:38:51
Block: 898794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330594 RingCT/type: yes/0
Extra: 014d2ed613436171ce3694a48ff83c04eef63496ee23e5eb7ecb1850b27eb1bc3e021100000009faf35c9c000000000000000000

1 output(s) for total of 0.645538808000 dcy

stealth address amount amount idx
00: 0ed1c2bbfd98114f5754d9042288dc21edae138eaabc1b1f5efd9c5f908b7078 0.645538808000 1355229 of 0

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": 898804, "vin": [ { "gen": { "height": 898794 } } ], "vout": [ { "amount": 645538808, "target": { "key": "0ed1c2bbfd98114f5754d9042288dc21edae138eaabc1b1f5efd9c5f908b7078" } } ], "extra": [ 1, 77, 46, 214, 19, 67, 97, 113, 206, 54, 148, 164, 143, 248, 60, 4, 238, 246, 52, 150, 238, 35, 229, 235, 126, 203, 24, 80, 178, 126, 177, 188, 62, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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