Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f071fec5d3e16a506d0dd2b2333141f9a7c66c909dd3bd5ee2f1685fef90ad1d

Tx prefix hash: b02d492f3896ee763212cb1e12a551d0121e977526a17abe15d94642bd404aef
Tx public key: c83a81d469361d50d914dbf06e25253655d5bbfb4673ff3cba907e414b077eb5
Timestamp: 1725383873 Timestamp [UCT]: 2024-09-03 17:17:53 Age [y:d:h:m:s]: 00:262:15:51:43
Block: 1102191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187615 RingCT/type: yes/0
Extra: 01c83a81d469361d50d914dbf06e25253655d5bbfb4673ff3cba907e414b077eb5021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32ae4be469d983bb4b75d46cbac33a85eae251e85499b8ae3a0eab8c07330fc2 0.600000000000 1578532 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": 1102201, "vin": [ { "gen": { "height": 1102191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32ae4be469d983bb4b75d46cbac33a85eae251e85499b8ae3a0eab8c07330fc2" } } ], "extra": [ 1, 200, 58, 129, 212, 105, 54, 29, 80, 217, 20, 219, 240, 110, 37, 37, 54, 85, 213, 187, 251, 70, 115, 255, 60, 186, 144, 126, 65, 75, 7, 126, 181, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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