Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2538a1c7875089ce6af8adf21648955aa7fdf7f6668c9e692ef3afc3513632f3

Tx prefix hash: 06a32ae0f5eb309329d31a7c32309b770415d10bd134d75e6d6f041f30662d15
Tx public key: 64a146067e5773ddd61bab3bc02728d83caee6e7c25ef9ad45e18c0a4f67b767
Timestamp: 1725049486 Timestamp [UCT]: 2024-08-30 20:24:46 Age [y:d:h:m:s]: 00:221:12:00:27
Block: 1099412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158168 RingCT/type: yes/0
Extra: 0164a146067e5773ddd61bab3bc02728d83caee6e7c25ef9ad45e18c0a4f67b767021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e2cd563538b49dfc3dbb7ad3b55213c779a6364b2b93e93cc2d2576f69b49b7 0.600000000000 1575373 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": 1099422, "vin": [ { "gen": { "height": 1099412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e2cd563538b49dfc3dbb7ad3b55213c779a6364b2b93e93cc2d2576f69b49b7" } } ], "extra": [ 1, 100, 161, 70, 6, 126, 87, 115, 221, 214, 27, 171, 59, 192, 39, 40, 216, 60, 174, 230, 231, 194, 94, 249, 173, 69, 225, 140, 10, 79, 103, 183, 103, 2, 17, 0, 0, 0, 3, 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