Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b173dd99ae620c6c4bd6bd2c36910a92c90aa54c55c3e931ccdc7a9119978e1e

Tx prefix hash: 74024f19d8d526e06345c897d1a5be05b0563adc0f62f2cd0a5d24d80d94423f
Tx public key: 0c436833f778d4eb2f73a4af70df7e01b3a3ba9b6ac9b9c5468879f4da8f08d7
Timestamp: 1708374810 Timestamp [UCT]: 2024-02-19 20:33:30 Age [y:d:h:m:s]: 01:075:07:57:25
Block: 961176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314880 RingCT/type: yes/0
Extra: 010c436833f778d4eb2f73a4af70df7e01b3a3ba9b6ac9b9c5468879f4da8f08d70211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a95efe335a61ef6c488781355d11196cf8c261fe84d007f672587c1ea72a4e09 0.600000000000 1420765 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": 961186, "vin": [ { "gen": { "height": 961176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a95efe335a61ef6c488781355d11196cf8c261fe84d007f672587c1ea72a4e09" } } ], "extra": [ 1, 12, 67, 104, 51, 247, 120, 212, 235, 47, 115, 164, 175, 112, 223, 126, 1, 179, 163, 186, 155, 106, 201, 185, 197, 70, 136, 121, 244, 218, 143, 8, 215, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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