Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b8e386195797e80192898e63641acf9928b72fd32f41aa93787bdc59b79f607

Tx prefix hash: 3033d4667d8368c24e764a4f6a8c1c33074cef207c276f5e3433ffb7b127db3d
Tx public key: 3c7bdd63895b4ec668ff2eee5fc5180ebc1d79e8e870f3c7bcba36a341d4669f
Timestamp: 1718585697 Timestamp [UCT]: 2024-06-17 00:54:57 Age [y:d:h:m:s]: 00:285:05:13:41
Block: 1045844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203799 RingCT/type: yes/0
Extra: 013c7bdd63895b4ec668ff2eee5fc5180ebc1d79e8e870f3c7bcba36a341d4669f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c41f8d6f5874136db1237b6393ad607cb917bb0a310c80d264f884c304e9ea2d 0.600000000000 1515535 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": 1045854, "vin": [ { "gen": { "height": 1045844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c41f8d6f5874136db1237b6393ad607cb917bb0a310c80d264f884c304e9ea2d" } } ], "extra": [ 1, 60, 123, 221, 99, 137, 91, 78, 198, 104, 255, 46, 238, 95, 197, 24, 14, 188, 29, 121, 232, 232, 112, 243, 199, 188, 186, 54, 163, 65, 212, 102, 159, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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