Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e955cacdc57ba16fb3cc2c6b24911ac3c6b37dc27a60f2ab636e37da59c0461

Tx prefix hash: 96d16cb5e6e621fb43a0bc17db486e748266eeaf7a5acd8f71300a5c46580191
Tx public key: 330c51f318213c2175334e1596e1e4ac24f43212db3260fbdf1b78b47c21a008
Timestamp: 1717703658 Timestamp [UCT]: 2024-06-06 19:54:18 Age [y:d:h:m:s]: 00:294:15:07:14
Block: 1038522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210552 RingCT/type: yes/0
Extra: 01330c51f318213c2175334e1596e1e4ac24f43212db3260fbdf1b78b47c21a00802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc1b78d462f62fe702807936a32a18b299e7a295a3212eb5de7bfb217d0aa2f6 0.600000000000 1507083 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": 1038532, "vin": [ { "gen": { "height": 1038522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc1b78d462f62fe702807936a32a18b299e7a295a3212eb5de7bfb217d0aa2f6" } } ], "extra": [ 1, 51, 12, 81, 243, 24, 33, 60, 33, 117, 51, 78, 21, 150, 225, 228, 172, 36, 244, 50, 18, 219, 50, 96, 251, 223, 27, 120, 180, 124, 33, 160, 8, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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