Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68cceebf39e6db8f63f76ea7eb31e74db507897dbaa10212881768c6eae38a07

Tx prefix hash: e18b9f43eaaf84ae37941dd02c78c17cfa8934d486d202a97c6659208d6f7eee
Tx public key: b961363111a08ee60ebb015a974cb96569dc1f8f2dc66057bc72fec28cb20bdd
Timestamp: 1699497600 Timestamp [UCT]: 2023-11-09 02:40:00 Age [y:d:h:m:s]: 01:155:21:06:47
Block: 887587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372588 RingCT/type: yes/0
Extra: 01b961363111a08ee60ebb015a974cb96569dc1f8f2dc66057bc72fec28cb20bdd021100000001679a8a81000000000000000000

1 output(s) for total of 0.703162685000 dcy

stealth address amount amount idx
00: 910cabca44185f5eb07736e3dc373be1fea4e7271770e5bf94a1bcf9a8cbb26d 0.703162685000 1343474 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": 887597, "vin": [ { "gen": { "height": 887587 } } ], "vout": [ { "amount": 703162685, "target": { "key": "910cabca44185f5eb07736e3dc373be1fea4e7271770e5bf94a1bcf9a8cbb26d" } } ], "extra": [ 1, 185, 97, 54, 49, 17, 160, 142, 230, 14, 187, 1, 90, 151, 76, 185, 101, 105, 220, 31, 143, 45, 198, 96, 87, 188, 114, 254, 194, 140, 178, 11, 221, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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