Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17fca9ebde61382593463ff6ce817bdb5b5cb4cf253326c99a523b94922ab1cb

Tx prefix hash: c2702d6111effd2a409e9481bab4cadbac8bc3277a070e14192224464af5637b
Tx public key: 3a71c3ef4e469fcd7a6db9e514b5f4a09ea4a579fa409df601a19358875d0234
Timestamp: 1583420354 Timestamp [UCT]: 2020-03-05 14:59:14 Age [y:d:h:m:s]: 04:332:10:21:22
Block: 76729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132005 RingCT/type: yes/0
Extra: 013a71c3ef4e469fcd7a6db9e514b5f4a09ea4a579fa409df601a19358875d0234021100000004026b59f3000000000000000000

1 output(s) for total of 341.800957793000 dcy

stealth address amount amount idx
00: 1d6879f4b18c0680551eb6ae8f21b41c29802450939fb778444af47aff37db21 341.800957793000 141235 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": 76739, "vin": [ { "gen": { "height": 76729 } } ], "vout": [ { "amount": 341800957793, "target": { "key": "1d6879f4b18c0680551eb6ae8f21b41c29802450939fb778444af47aff37db21" } } ], "extra": [ 1, 58, 113, 195, 239, 78, 70, 159, 205, 122, 109, 185, 229, 20, 181, 244, 160, 158, 164, 165, 121, 250, 64, 157, 246, 1, 161, 147, 88, 135, 93, 2, 52, 2, 17, 0, 0, 0, 4, 2, 107, 89, 243, 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