Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07eb0a84e714b7471b9de4648661afbe22d157ab7a9352d3f12b069feaa87f5a

Tx prefix hash: 4f9536a7a1729bd50462e4d3df063c2255fac7af699204b441a602ebc0d97ec5
Tx public key: b2ade1fcc8833b93cd5c2ed1aaf0c944d9086d4bbfaaeed723674b0aa4ad5b46
Timestamp: 1721097292 Timestamp [UCT]: 2024-07-16 02:34:52 Age [y:d:h:m:s]: 00:255:22:49:55
Block: 1066669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182838 RingCT/type: yes/0
Extra: 01b2ade1fcc8833b93cd5c2ed1aaf0c944d9086d4bbfaaeed723674b0aa4ad5b4602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2eb431ebd91a510afedb031589449bd1ac4e5fe563df715f7ca85e86c90c623 0.600000000000 1537336 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": 1066679, "vin": [ { "gen": { "height": 1066669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2eb431ebd91a510afedb031589449bd1ac4e5fe563df715f7ca85e86c90c623" } } ], "extra": [ 1, 178, 173, 225, 252, 200, 131, 59, 147, 205, 92, 46, 209, 170, 240, 201, 68, 217, 8, 109, 75, 191, 170, 238, 215, 35, 103, 75, 10, 164, 173, 91, 70, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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