Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 031ebdfbf02d02b0c6891caf3cd1ba6f19f49b72505c34bed7dfe468a5d368b5

Tx prefix hash: d5581ebe4cc90475420ea4960c71b8e1b383115592aa38c1d9d5d66b0bdd65d0
Tx public key: b1d6060e59878030cf56653d09d58ded4e9ccae0e847acd5f2259250d39e574e
Timestamp: 1727572703 Timestamp [UCT]: 2024-09-29 01:18:23 Age [y:d:h:m:s]: 01:043:01:37:49
Block: 1120338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289174 RingCT/type: yes/0
Extra: 01b1d6060e59878030cf56653d09d58ded4e9ccae0e847acd5f2259250d39e574e02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c15fa220c6e234dad833cb22727094be5e6c75585c07ee4f2b968a16e6c376a 0.600000000000 1602219 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": 1120348, "vin": [ { "gen": { "height": 1120338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c15fa220c6e234dad833cb22727094be5e6c75585c07ee4f2b968a16e6c376a" } } ], "extra": [ 1, 177, 214, 6, 14, 89, 135, 128, 48, 207, 86, 101, 61, 9, 213, 141, 237, 78, 156, 202, 224, 232, 71, 172, 213, 242, 37, 146, 80, 211, 158, 87, 78, 2, 17, 0, 0, 0, 4, 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