Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21083de7d2c68dab2846b94bf080bb70af9ba4ce6dc2da57c01315a46639291a

Tx prefix hash: d1b0cf4b2cd340ee170e4d2819805e2d6239d69b3b1143e7ec8026145ba047a4
Tx public key: 4e0a64dc3cacf82bf5ea362944c640b9fba9cdfeb7b860edc1f634776aa7f51f
Timestamp: 1717296152 Timestamp [UCT]: 2024-06-02 02:42:32 Age [y:d:h:m:s]: 00:305:16:17:55
Block: 1035144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218452 RingCT/type: yes/0
Extra: 014e0a64dc3cacf82bf5ea362944c640b9fba9cdfeb7b860edc1f634776aa7f51f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30b39500f820c17424afe6b52440af38a2b2d3eb0dc3c95c661371b2f20ddf88 0.600000000000 1503663 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": 1035154, "vin": [ { "gen": { "height": 1035144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30b39500f820c17424afe6b52440af38a2b2d3eb0dc3c95c661371b2f20ddf88" } } ], "extra": [ 1, 78, 10, 100, 220, 60, 172, 248, 43, 245, 234, 54, 41, 68, 198, 64, 185, 251, 169, 205, 254, 183, 184, 96, 237, 193, 246, 52, 119, 106, 167, 245, 31, 2, 17, 0, 0, 0, 1, 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