Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd5f83c7c8a094411e1fa65bbd925792b41361f9f2eb73484e0e929e41135527

Tx prefix hash: 50176a59fb3a16bf6a1905934c998e8aaedb2fb380b556e7466d0f5b512dc9ea
Tx public key: fa6e17c45a5894257e627c5a55b5a033a365c03d0131d0f38bf369257042708f
Timestamp: 1701923245 Timestamp [UCT]: 2023-12-07 04:27:25 Age [y:d:h:m:s]: 01:120:19:30:47
Block: 907689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347492 RingCT/type: yes/0
Extra: 01fa6e17c45a5894257e627c5a55b5a033a365c03d0131d0f38bf369257042708f02110000000539e1d5d3000000000000000000

1 output(s) for total of 0.603183587000 dcy

stealth address amount amount idx
00: 1e53644669e487d8a504c074b7c1def632a9cb6c4b7a649869355ea6a1d3c73d 0.603183587000 1364682 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": 907699, "vin": [ { "gen": { "height": 907689 } } ], "vout": [ { "amount": 603183587, "target": { "key": "1e53644669e487d8a504c074b7c1def632a9cb6c4b7a649869355ea6a1d3c73d" } } ], "extra": [ 1, 250, 110, 23, 196, 90, 88, 148, 37, 126, 98, 124, 90, 85, 181, 160, 51, 163, 101, 192, 61, 1, 49, 208, 243, 139, 243, 105, 37, 112, 66, 112, 143, 2, 17, 0, 0, 0, 5, 57, 225, 213, 211, 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