Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f78c6fee736a55e8335a069d4589cd88533d99be2c086707675dc5a42ce52b81

Tx prefix hash: 70753fd441bae06e618d6a014d1a675e17196c3df97c03c6b91a951c9787cdd6
Tx public key: 8db1b9fa1bb6e600cc4b657bb613cb72671dc22a9089603ea6a067b9861c663b
Timestamp: 1657125211 Timestamp [UCT]: 2022-07-06 16:33:31 Age [y:d:h:m:s]: 02:185:04:46:17
Block: 537990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 653720 RingCT/type: yes/0
Extra: 018db1b9fa1bb6e600cc4b657bb613cb72671dc22a9089603ea6a067b9861c663b02110000000a4da16a3a000000000000000000

1 output(s) for total of 10.125487680000 dcy

stealth address amount amount idx
00: 2f33ef49aa327c69548b6be355c4e3d335de0efa8739ca0fa462a8d416e05640 10.125487680000 967937 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": 538000, "vin": [ { "gen": { "height": 537990 } } ], "vout": [ { "amount": 10125487680, "target": { "key": "2f33ef49aa327c69548b6be355c4e3d335de0efa8739ca0fa462a8d416e05640" } } ], "extra": [ 1, 141, 177, 185, 250, 27, 182, 230, 0, 204, 75, 101, 123, 182, 19, 203, 114, 103, 29, 194, 42, 144, 137, 96, 62, 166, 160, 103, 185, 134, 28, 102, 59, 2, 17, 0, 0, 0, 10, 77, 161, 106, 58, 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