Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dd28b0263e8ab2e2d8f7f6e1bd905a5771826d2ccc79c9f02cb776b8a76be3d

Tx prefix hash: 5b2429068e7ded788453a7d49fe388baeb8da2d45259327d1828945331ebac10
Tx public key: 9afb6ee930e8d780553e948aa174cbda37a1bfaeeb2a0b2001e779a61a2ac5a2
Timestamp: 1708092113 Timestamp [UCT]: 2024-02-16 14:01:53 Age [y:d:h:m:s]: 01:010:02:23:03
Block: 958831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268220 RingCT/type: yes/0
Extra: 019afb6ee930e8d780553e948aa174cbda37a1bfaeeb2a0b2001e779a61a2ac5a202110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e67e515ef8ddd56e6c231be1098c7767f1725daf004f1ab21943ab833060e18 0.600000000000 1418196 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": 958841, "vin": [ { "gen": { "height": 958831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e67e515ef8ddd56e6c231be1098c7767f1725daf004f1ab21943ab833060e18" } } ], "extra": [ 1, 154, 251, 110, 233, 48, 232, 215, 128, 85, 62, 148, 138, 161, 116, 203, 218, 55, 161, 191, 174, 235, 42, 11, 32, 1, 231, 121, 166, 26, 42, 197, 162, 2, 17, 0, 0, 0, 9, 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