Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a952c3701064a6ba5c54a11f8dbc9e41ff3618350b138e37ad45e0935a5f0a

Tx prefix hash: 0b7bcb9cc76e24ff9cd2acfdbf0113ce5f11d2e10537448689f584290ac2f6ce
Tx public key: 40b4527fb5e51466d1337c24b7749c978f03e5ff16f157e0a037fa98e7852d9a
Timestamp: 1680969523 Timestamp [UCT]: 2023-04-08 15:58:43 Age [y:d:h:m:s]: 01:280:02:52:52
Block: 734288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461641 RingCT/type: yes/0
Extra: 0140b4527fb5e51466d1337c24b7749c978f03e5ff16f157e0a037fa98e7852d9a021100000003b3164c24000000000000000000

1 output(s) for total of 2.264640473000 dcy

stealth address amount amount idx
00: 0d844b481e189471fa10d03ca46e9edb277b6088e88b4a3d9675fa3c70029191 2.264640473000 1180469 of 0

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": 734298, "vin": [ { "gen": { "height": 734288 } } ], "vout": [ { "amount": 2264640473, "target": { "key": "0d844b481e189471fa10d03ca46e9edb277b6088e88b4a3d9675fa3c70029191" } } ], "extra": [ 1, 64, 180, 82, 127, 181, 229, 20, 102, 209, 51, 124, 36, 183, 116, 156, 151, 143, 3, 229, 255, 22, 241, 87, 224, 160, 55, 250, 152, 231, 133, 45, 154, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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