Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f11bdeeaed019764d35dda1d51f1826f4b14bb7c784337abcb1b1f166c24f2fd

Tx prefix hash: 9b2d8719f5d841b9ff4053c078357d17066e2f9337f5a95065b651696ffe169c
Tx public key: 8d61e95202d8a7d9d407035a6cf8c9ddd5a0ccc54912dd4a6d848cec8946da9f
Timestamp: 1581086045 Timestamp [UCT]: 2020-02-07 14:34:05 Age [y:d:h:m:s]: 04:325:12:45:10
Block: 60333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124397 RingCT/type: yes/0
Extra: 018d61e95202d8a7d9d407035a6cf8c9ddd5a0ccc54912dd4a6d848cec8946da9f021100000001c71d3ff9000000000000000000

1 output(s) for total of 387.340174100000 dcy

stealth address amount amount idx
00: c356813278bdf6a2e4fb483b68fd1ff4d1b0952608a1a1c034de960ec8edbcb3 387.340174100000 111237 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": 60343, "vin": [ { "gen": { "height": 60333 } } ], "vout": [ { "amount": 387340174100, "target": { "key": "c356813278bdf6a2e4fb483b68fd1ff4d1b0952608a1a1c034de960ec8edbcb3" } } ], "extra": [ 1, 141, 97, 233, 82, 2, 216, 167, 217, 212, 7, 3, 90, 108, 248, 201, 221, 213, 160, 204, 197, 73, 18, 221, 74, 109, 132, 140, 236, 137, 70, 218, 159, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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