Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1c9504259e6f0f7e5085c5ab29fc6f91e6d1374c65417d22ce3aa57d7885dff

Tx prefix hash: 13767fe64ce1608ff7388812909f5c4ab509188d9b0ead505a39c6a2d4073152
Tx public key: eb0c1693a65f7652fc2b484414de9640bfa37b699565447e85b60a3e2b7edd9b
Timestamp: 1708367722 Timestamp [UCT]: 2024-02-19 18:35:22 Age [y:d:h:m:s]: 01:287:23:28:38
Block: 961112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464611 RingCT/type: yes/0
Extra: 01eb0c1693a65f7652fc2b484414de9640bfa37b699565447e85b60a3e2b7edd9b02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 854a3c673365b99c7ccaceb9dffb3d340cd84278d105e9fa13b061313a20f94d 0.600000000000 1420699 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": 961122, "vin": [ { "gen": { "height": 961112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "854a3c673365b99c7ccaceb9dffb3d340cd84278d105e9fa13b061313a20f94d" } } ], "extra": [ 1, 235, 12, 22, 147, 166, 95, 118, 82, 252, 43, 72, 68, 20, 222, 150, 64, 191, 163, 123, 105, 149, 101, 68, 126, 133, 182, 10, 62, 43, 126, 221, 155, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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