Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd104d5b637bb6be9a4a2e8ed5d26f2ebfb17b5cabe9409e9acab4b150086d42

Tx prefix hash: 7fcc4702754e056c5d119b13b4c103b8c6555f02b2771aea12e2f388a1c08425
Tx public key: c9a31e23f3eaed202f1553684e89d1b90100a2c2b84ec1ec4ce2099b35114309
Timestamp: 1710768170 Timestamp [UCT]: 2024-03-18 13:22:50 Age [y:d:h:m:s]: 00:339:20:47:35
Block: 981033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242963 RingCT/type: yes/0
Extra: 01c9a31e23f3eaed202f1553684e89d1b90100a2c2b84ec1ec4ce2099b3511430902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c345bebc858afcb86f412259ba09c3b56fea719f94db8d31257714e7f16acca3 0.600000000000 1441118 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": 981043, "vin": [ { "gen": { "height": 981033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c345bebc858afcb86f412259ba09c3b56fea719f94db8d31257714e7f16acca3" } } ], "extra": [ 1, 201, 163, 30, 35, 243, 234, 237, 32, 47, 21, 83, 104, 78, 137, 209, 185, 1, 0, 162, 194, 184, 78, 193, 236, 76, 226, 9, 155, 53, 17, 67, 9, 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