Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f35c8039eceaf8117376de658eafbeec43dbd4eae6a5e1f6c73b830db25e36e

Tx prefix hash: 67781bd7b4c7d3fb025d5f6ddf7308405881756e2195206683a26919371078b1
Tx public key: 107a9ff31ede3e2aea4aed3e95ede4418c31c67dcb9ca2aafb1e6a3845b9f8d9
Timestamp: 1709249805 Timestamp [UCT]: 2024-02-29 23:36:45 Age [y:d:h:m:s]: 01:059:12:41:20
Block: 968442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303568 RingCT/type: yes/0
Extra: 01107a9ff31ede3e2aea4aed3e95ede4418c31c67dcb9ca2aafb1e6a3845b9f8d902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6880fd0e98d88d92603b9651b70c6d0d53ffc063c1558d64b32ec0c33e40e78a 0.600000000000 1428257 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": 968452, "vin": [ { "gen": { "height": 968442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6880fd0e98d88d92603b9651b70c6d0d53ffc063c1558d64b32ec0c33e40e78a" } } ], "extra": [ 1, 16, 122, 159, 243, 30, 222, 62, 42, 234, 74, 237, 62, 149, 237, 228, 65, 140, 49, 198, 125, 203, 156, 162, 170, 251, 30, 106, 56, 69, 185, 248, 217, 2, 17, 0, 0, 0, 3, 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