Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 282b412c9deb0eabd59e1e688d4e9781941d382948b191cd1d5cb78ea206396a

Tx prefix hash: 8be3626f4eb1641e9041a0ecf4275f399b1344c2944dd56fd76d65e0a8441556
Tx public key: 8dbfdcfef02182b3b759593f232b8d19625f0e205c83b9a89868e8ff7614ae3f
Timestamp: 1737006943 Timestamp [UCT]: 2025-01-16 05:55:43 Age [y:d:h:m:s]: 00:153:12:48:07
Block: 1198393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109434 RingCT/type: yes/0
Extra: 018dbfdcfef02182b3b759593f232b8d19625f0e205c83b9a89868e8ff7614ae3f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 216b0452a974b72e05093f33402a9cd9a7b63f65cf2557e78689ab73c629cf74 0.600000000000 1685018 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": 1198403, "vin": [ { "gen": { "height": 1198393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "216b0452a974b72e05093f33402a9cd9a7b63f65cf2557e78689ab73c629cf74" } } ], "extra": [ 1, 141, 191, 220, 254, 240, 33, 130, 179, 183, 89, 89, 63, 35, 43, 141, 25, 98, 95, 14, 32, 92, 131, 185, 168, 152, 104, 232, 255, 118, 20, 174, 63, 2, 17, 0, 0, 0, 1, 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