Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1738fd1387dab2a57f01e833f39f72429d7f4262d50ef88601d4d1f4868f5ca5

Tx prefix hash: a02d0a7fc770734cc3c4881b61000cd255387a79dc0e8f8f3123e620db41ba0d
Tx public key: 66f259affa0945d9a5ea360b6e3c0dcc1429a91bee87988fce5bca38ef50baa2
Timestamp: 1673889181 Timestamp [UCT]: 2023-01-16 17:13:01 Age [y:d:h:m:s]: 02:100:22:41:43
Block: 676127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593840 RingCT/type: yes/0
Extra: 0166f259affa0945d9a5ea360b6e3c0dcc1429a91bee87988fce5bca38ef50baa202110000000152542ceb000000000000000000

1 output(s) for total of 3.529478361000 dcy

stealth address amount amount idx
00: 8144dc9f4fb8c4fbb54923583b367c51fdbdb48e228509872dd81b663d154ce7 3.529478361000 1117836 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": 676137, "vin": [ { "gen": { "height": 676127 } } ], "vout": [ { "amount": 3529478361, "target": { "key": "8144dc9f4fb8c4fbb54923583b367c51fdbdb48e228509872dd81b663d154ce7" } } ], "extra": [ 1, 102, 242, 89, 175, 250, 9, 69, 217, 165, 234, 54, 11, 110, 60, 13, 204, 20, 41, 169, 27, 238, 135, 152, 143, 206, 91, 202, 56, 239, 80, 186, 162, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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