Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddf8dea64071d1cfd31c70ad211e6565aeb69921d5fcf1c98cd995bcf411241e

Tx prefix hash: 1d386e7c413a658c5483f115faa894f84c5de48f587b9c8b52b69eb8537b42bc
Tx public key: 19378e980db45a7c26e5d4f4e4e2e24e24e62e4619c026450da8dbe5310f64d4
Timestamp: 1755287027 Timestamp [UCT]: 2025-08-15 19:43:47 Age [y:d:h:m:s]: 00:102:19:54:54
Block: 1347396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73236 RingCT/type: yes/0
Extra: 0119378e980db45a7c26e5d4f4e4e2e24e24e62e4619c026450da8dbe5310f64d402110000000bb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92ba05fdf7679bdbaa2810cedbc4a81d1c70635108656ffc9720144e7a34070d 0.600000000000 1835313 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": 1347406, "vin": [ { "gen": { "height": 1347396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92ba05fdf7679bdbaa2810cedbc4a81d1c70635108656ffc9720144e7a34070d" } } ], "extra": [ 1, 25, 55, 142, 152, 13, 180, 90, 124, 38, 229, 212, 244, 228, 226, 226, 78, 36, 230, 46, 70, 25, 192, 38, 69, 13, 168, 219, 229, 49, 15, 100, 212, 2, 17, 0, 0, 0, 11, 178, 247, 132, 196, 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