Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67ac1b968899c4bd8352cce187b2fd6631c21393baf91fe99ec9cd049859f894

Tx prefix hash: c1fbd7c3e40fbb12c0572003cf75c621c1ed42978b3e76d986cbab9ba972c0a9
Tx public key: f97c751d6f2f5be63e4a61bdb06d5613cce823eea4432c0f348aa1276a85aac7
Timestamp: 1713159855 Timestamp [UCT]: 2024-04-15 05:44:15 Age [y:d:h:m:s]: 00:336:22:00:42
Block: 1000837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240877 RingCT/type: yes/0
Extra: 01f97c751d6f2f5be63e4a61bdb06d5613cce823eea4432c0f348aa1276a85aac702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5dc514d65b955a3a43dd1e6a719d547dad4ed01b998e9b4ed79bfaf9400ea337 0.600000000000 1461337 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": 1000847, "vin": [ { "gen": { "height": 1000837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5dc514d65b955a3a43dd1e6a719d547dad4ed01b998e9b4ed79bfaf9400ea337" } } ], "extra": [ 1, 249, 124, 117, 29, 111, 47, 91, 230, 62, 74, 97, 189, 176, 109, 86, 19, 204, 232, 35, 238, 164, 67, 44, 15, 52, 138, 161, 39, 106, 133, 170, 199, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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