Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ada643ad2b43fa9a3db67560e52bbdc335a1a9a661bff54af6c4c0d5fabfe32

Tx prefix hash: b10bf3b07f69324c10e2510369b8bd62de894f84039b1e26f991caac348519ba
Tx public key: 53772797d8349bc5cec812e84f92dc16cbb6d6b21efb4bdb98b127a7432a43ff
Timestamp: 1740770105 Timestamp [UCT]: 2025-02-28 19:15:05 Age [y:d:h:m:s]: 00:265:01:17:58
Block: 1229281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187190 RingCT/type: yes/0
Extra: 0153772797d8349bc5cec812e84f92dc16cbb6d6b21efb4bdb98b127a7432a43ff021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c396d77fcad68c2ad7768bc328e77a7f29d1e28695c9d0c58734174f78dbaf41 0.600000000000 1716166 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": 1229291, "vin": [ { "gen": { "height": 1229281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c396d77fcad68c2ad7768bc328e77a7f29d1e28695c9d0c58734174f78dbaf41" } } ], "extra": [ 1, 83, 119, 39, 151, 216, 52, 155, 197, 206, 200, 18, 232, 79, 146, 220, 22, 203, 182, 214, 178, 30, 251, 75, 219, 152, 177, 39, 167, 67, 42, 67, 255, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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