Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aecb3a9ff28237b14851de0f983c7e5da1b70bf5b73475ebcfb7f0198778d26f

Tx prefix hash: 96e098780ad9d8c435b773b5a1340359a40cdb40231647e3d9f6a116810a7c59
Tx public key: 4568c2372325876663e87abced152f55fa4d76e3d1ea19dbc22c7710b8c300a4
Timestamp: 1735883085 Timestamp [UCT]: 2025-01-03 05:44:45 Age [y:d:h:m:s]: 00:080:08:45:50
Block: 1189112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57205 RingCT/type: yes/0
Extra: 014568c2372325876663e87abced152f55fa4d76e3d1ea19dbc22c7710b8c300a4021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 832550e601679b82987d34bef7e943706c34f4a76a3aa8e29b76e5197f615f69 0.600000000000 1675617 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": 1189122, "vin": [ { "gen": { "height": 1189112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "832550e601679b82987d34bef7e943706c34f4a76a3aa8e29b76e5197f615f69" } } ], "extra": [ 1, 69, 104, 194, 55, 35, 37, 135, 102, 99, 232, 122, 188, 237, 21, 47, 85, 250, 77, 118, 227, 209, 234, 25, 219, 194, 44, 119, 16, 184, 195, 0, 164, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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