Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47147fd42e3b9dfb71a26dd0fd2376dccc750965cace3722fd7e877265dc4bdb

Tx prefix hash: 1c7dffd47a75c3d703ff491068bd5d59b3b204e13db679c4dbb9908f996f3146
Tx public key: 355505b04604b2c2079fd464ddc405bfc47231a2334f7383d44cc32f709b340c
Timestamp: 1732775422 Timestamp [UCT]: 2024-11-28 06:30:22 Age [y:d:h:m:s]: 00:111:05:08:35
Block: 1163367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79308 RingCT/type: yes/0
Extra: 01355505b04604b2c2079fd464ddc405bfc47231a2334f7383d44cc32f709b340c0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 858eba4c851e3ebd07f7c5c035060bfb358085c5a8e6acbb8f3be09973529df0 0.600000000000 1649034 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": 1163377, "vin": [ { "gen": { "height": 1163367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "858eba4c851e3ebd07f7c5c035060bfb358085c5a8e6acbb8f3be09973529df0" } } ], "extra": [ 1, 53, 85, 5, 176, 70, 4, 178, 194, 7, 159, 212, 100, 221, 196, 5, 191, 196, 114, 49, 162, 51, 79, 115, 131, 212, 76, 195, 47, 112, 155, 52, 12, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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