Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d98ecdbff870581867318415c1d9988ad468f9d3699e0f0d7218e843bb7f14cb

Tx prefix hash: 653f9c6ce6717f1471815a4c90595b704374e768daa51d25ef5292613297a30f
Tx public key: 02a1c6de5c81ff32f8ad864a99764211524dc94f4244a8cc4dfd0dc98f7af57d
Timestamp: 1705920925 Timestamp [UCT]: 2024-01-22 10:55:25 Age [y:d:h:m:s]: 01:143:19:59:07
Block: 940801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363870 RingCT/type: yes/0
Extra: 0102a1c6de5c81ff32f8ad864a99764211524dc94f4244a8cc4dfd0dc98f7af57d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0f73a05b2e19650083cad826c8bd6c78b25a57aaf23467fd0905bedc2bbf4cc 0.600000000000 1398941 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": 940811, "vin": [ { "gen": { "height": 940801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0f73a05b2e19650083cad826c8bd6c78b25a57aaf23467fd0905bedc2bbf4cc" } } ], "extra": [ 1, 2, 161, 198, 222, 92, 129, 255, 50, 248, 173, 134, 74, 153, 118, 66, 17, 82, 77, 201, 79, 66, 68, 168, 204, 77, 253, 13, 201, 143, 122, 245, 125, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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