Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e58fd4ee992d89082860117a4a4efaf31df5e349152499b22b6c6ad159ee3672

Tx prefix hash: b2fe36aa377e62bda0d83a31fe3c1a9b799660dd5fb14575fae98f42f4d0611b
Tx public key: 2a7afcfb0404e924a690d9565935edca59322c2e8003b88e23f3f8ed4a52e8f7
Timestamp: 1737944967 Timestamp [UCT]: 2025-01-27 02:29:27 Age [y:d:h:m:s]: 00:142:00:06:53
Block: 1205932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101425 RingCT/type: yes/0
Extra: 012a7afcfb0404e924a690d9565935edca59322c2e8003b88e23f3f8ed4a52e8f7021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5da829a00d423c446eecea9e16be061a27cb6596c7d17fd583d581503c3249fc 0.600000000000 1692631 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": 1205942, "vin": [ { "gen": { "height": 1205932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5da829a00d423c446eecea9e16be061a27cb6596c7d17fd583d581503c3249fc" } } ], "extra": [ 1, 42, 122, 252, 251, 4, 4, 233, 36, 166, 144, 217, 86, 89, 53, 237, 202, 89, 50, 44, 46, 128, 3, 184, 142, 35, 243, 248, 237, 74, 82, 232, 247, 2, 17, 0, 0, 0, 2, 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