Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a1fcd0d83b42085d27b0817223e75fb618f09061b023772663e4131a7cb9266

Tx prefix hash: b461728d920faf8be0bf7a40d4cc527dee6cbe46494528d1d6d30532d94d375d
Tx public key: 99667d719d8c819eb476105ddf82810116c58db4ea517ef058b3d6304fd693ed
Timestamp: 1734534750 Timestamp [UCT]: 2024-12-18 15:12:30 Age [y:d:h:m:s]: 00:111:16:06:07
Block: 1177969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79580 RingCT/type: yes/0
Extra: 0199667d719d8c819eb476105ddf82810116c58db4ea517ef058b3d6304fd693ed0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd5f655f0e6ff001b4e73f80ea5e17ce265cfd3b4a42d2db4f1b89dec62b5f56 0.600000000000 1664350 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": 1177979, "vin": [ { "gen": { "height": 1177969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd5f655f0e6ff001b4e73f80ea5e17ce265cfd3b4a42d2db4f1b89dec62b5f56" } } ], "extra": [ 1, 153, 102, 125, 113, 157, 140, 129, 158, 180, 118, 16, 93, 223, 130, 129, 1, 22, 197, 141, 180, 234, 81, 126, 240, 88, 179, 214, 48, 79, 214, 147, 237, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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