Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc74bcd97dba429c99045ff810dffc25dc474738c82ba2da32537a8e30f2d2cd

Tx prefix hash: a6aa540a53a914855a0c1775a5b043ada026d5d02fe70c6eecd7bd5bc65c7315
Tx public key: 17e1d69ca46b5a7b367b304f08efd62947f48a28d0941a3355351187469f80ac
Timestamp: 1717427968 Timestamp [UCT]: 2024-06-03 15:19:28 Age [y:d:h:m:s]: 00:347:10:20:45
Block: 1036246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248315 RingCT/type: yes/0
Extra: 0117e1d69ca46b5a7b367b304f08efd62947f48a28d0941a3355351187469f80ac02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e0be3c1078d0698e0d3aa9938d25036e2411cf0df513a3ccd93624d43d8d4cf 0.600000000000 1504771 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": 1036256, "vin": [ { "gen": { "height": 1036246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e0be3c1078d0698e0d3aa9938d25036e2411cf0df513a3ccd93624d43d8d4cf" } } ], "extra": [ 1, 23, 225, 214, 156, 164, 107, 90, 123, 54, 123, 48, 79, 8, 239, 214, 41, 71, 244, 138, 40, 208, 148, 26, 51, 85, 53, 17, 135, 70, 159, 128, 172, 2, 17, 0, 0, 0, 4, 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