Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea0ff6c8ce93f54a9b5860290dc87d367a835cbfcf4098c20215dafd38428a82

Tx prefix hash: d10101cd854d57bec421ba3dbe00bc98a7c1e577c22fdd9fca4381ce453626ef
Tx public key: 6b8c9457c72e2bf9411430c72feeef3af27984bcb7b14e9c30b38289167ed7b1
Timestamp: 1694260604 Timestamp [UCT]: 2023-09-09 11:56:44 Age [y:d:h:m:s]: 01:241:03:32:03
Block: 844341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433488 RingCT/type: yes/0
Extra: 016b8c9457c72e2bf9411430c72feeef3af27984bcb7b14e9c30b38289167ed7b1021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.978020210000 dcy

stealth address amount amount idx
00: a16e2e09aa35f753594c3bde0ba0f7460e1b9f47fbe6e0aeb032de91ffb3033d 0.978020210000 1297643 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": 844351, "vin": [ { "gen": { "height": 844341 } } ], "vout": [ { "amount": 978020210, "target": { "key": "a16e2e09aa35f753594c3bde0ba0f7460e1b9f47fbe6e0aeb032de91ffb3033d" } } ], "extra": [ 1, 107, 140, 148, 87, 199, 46, 43, 249, 65, 20, 48, 199, 47, 238, 239, 58, 242, 121, 132, 188, 183, 177, 78, 156, 48, 179, 130, 137, 22, 126, 215, 177, 2, 17, 0, 0, 0, 6, 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