Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe05cf76e45284c65610762de89cc8ee00e995845ed3680b3455c8c1cb962d1

Tx prefix hash: fbc68e8c2d49888e7371d95c61d8de9fddc44a24a2050f769eb2adfb169742eb
Tx public key: 3544c454b59af4ff8ceb75bc27d12c52631ee5959dde4aceaa1e0275d951afea
Timestamp: 1626883348 Timestamp [UCT]: 2021-07-21 16:02:28 Age [y:d:h:m:s]: 03:195:06:48:36
Block: 298334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 911039 RingCT/type: yes/0
Extra: 013544c454b59af4ff8ceb75bc27d12c52631ee5959dde4aceaa1e0275d951afea02110000001edc2edd98000000000000000000

1 output(s) for total of 63.022569606000 dcy

stealth address amount amount idx
00: dd3812a3e110fa0e7b2b545f7c492728612e13f3e7e7c3c161134c02984adbc8 63.022569606000 624165 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": 298344, "vin": [ { "gen": { "height": 298334 } } ], "vout": [ { "amount": 63022569606, "target": { "key": "dd3812a3e110fa0e7b2b545f7c492728612e13f3e7e7c3c161134c02984adbc8" } } ], "extra": [ 1, 53, 68, 196, 84, 181, 154, 244, 255, 140, 235, 117, 188, 39, 209, 44, 82, 99, 30, 229, 149, 157, 222, 74, 206, 170, 30, 2, 117, 217, 81, 175, 234, 2, 17, 0, 0, 0, 30, 220, 46, 221, 152, 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