Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4aa49c6b6055bced75d844414175a3e3c230051f42fc4d3fa1a47861632b8b42

Tx prefix hash: f8fdb4ffd100d3a770d08d6a9dd0a0e76121801689bb95b60b66c408d5a70e4a
Tx public key: a68b0a1f14d14ab3ecdeabd924ff86fd021c47ae14550725e35ef846a3ec225e
Timestamp: 1702396832 Timestamp [UCT]: 2023-12-12 16:00:32 Age [y:d:h:m:s]: 01:140:19:59:46
Block: 911636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361779 RingCT/type: yes/0
Extra: 01a68b0a1f14d14ab3ecdeabd924ff86fd021c47ae14550725e35ef846a3ec225e02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc9cd517962ad83c773a0c194238acc08ba1be20f7d54e4ff104b1a31029fcae 0.600000000000 1368850 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": 911646, "vin": [ { "gen": { "height": 911636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc9cd517962ad83c773a0c194238acc08ba1be20f7d54e4ff104b1a31029fcae" } } ], "extra": [ 1, 166, 139, 10, 31, 20, 209, 74, 179, 236, 222, 171, 217, 36, 255, 134, 253, 2, 28, 71, 174, 20, 85, 7, 37, 227, 94, 248, 70, 163, 236, 34, 94, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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