Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c58a7e45aed09ce7c96df756824d85f9c97128b3bf4c2db193a4e9ab8a2d4d5

Tx prefix hash: a50106cfef8885727f682f4b8c6b24c2e7d5830ee98efe2ceacaf8016a607354
Tx public key: 4417c650f35742cef931f751b46856a2dd5ee9ed1e745f686ae3bc085c5f4ea8
Timestamp: 1696290721 Timestamp [UCT]: 2023-10-02 23:52:01 Age [y:d:h:m:s]: 01:096:02:59:42
Block: 861195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329973 RingCT/type: yes/0
Extra: 014417c650f35742cef931f751b46856a2dd5ee9ed1e745f686ae3bc085c5f4ea8021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.860010010000 dcy

stealth address amount amount idx
00: ff12c84f134989ba0b99c2e7d56e43762d6867d66be5894467e45b8a4ec99d9a 0.860010010000 1315523 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": 861205, "vin": [ { "gen": { "height": 861195 } } ], "vout": [ { "amount": 860010010, "target": { "key": "ff12c84f134989ba0b99c2e7d56e43762d6867d66be5894467e45b8a4ec99d9a" } } ], "extra": [ 1, 68, 23, 198, 80, 243, 87, 66, 206, 249, 49, 247, 81, 180, 104, 86, 162, 221, 94, 233, 237, 30, 116, 95, 104, 106, 227, 188, 8, 92, 95, 78, 168, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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