Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51db2f5b5da0b60b2e8e2c6f03be781b05f4279ffe811d2a2fcc9c6c4e2bf9bc

Tx prefix hash: e05027e79bbf65387f012208e903b20e0c86723ad4a85d27cde6274d850e9cd7
Tx public key: 893e87b2a8eeba31bda70c5aedc704d00e992db1ca50b5b836b02b37b226ae09
Timestamp: 1725399430 Timestamp [UCT]: 2024-09-03 21:37:10 Age [y:d:h:m:s]: 00:172:06:57:39
Block: 1102319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122940 RingCT/type: yes/0
Extra: 01893e87b2a8eeba31bda70c5aedc704d00e992db1ca50b5b836b02b37b226ae09021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2ae4970a9ad5b074b036995a8d971d08df33efc03fedafec7e60be1577b75f8 0.600000000000 1578710 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": 1102329, "vin": [ { "gen": { "height": 1102319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2ae4970a9ad5b074b036995a8d971d08df33efc03fedafec7e60be1577b75f8" } } ], "extra": [ 1, 137, 62, 135, 178, 168, 238, 186, 49, 189, 167, 12, 90, 237, 199, 4, 208, 14, 153, 45, 177, 202, 80, 181, 184, 54, 176, 43, 55, 178, 38, 174, 9, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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