Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 657bc33e41f0d181b89a1e9ba64657844a9019378489805e445e706463146b64

Tx prefix hash: 123e5d612d4422cfecdbcc2e8ca3e32087a3ef913d7a57203400afe9b5cadfef
Tx public key: d1877879c6f0c7f9a5d87984750a29686252df6f404ce5c6da7a3d891042c139
Timestamp: 1704514487 Timestamp [UCT]: 2024-01-06 04:14:47 Age [y:d:h:m:s]: 01:102:20:37:41
Block: 929143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334636 RingCT/type: yes/0
Extra: 01d1877879c6f0c7f9a5d87984750a29686252df6f404ce5c6da7a3d891042c139021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65ed0d5c9ebcd042797fe4c1e74da88e22f6a5429dbed174b126503f8194dd32 0.600000000000 1387011 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": 929153, "vin": [ { "gen": { "height": 929143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65ed0d5c9ebcd042797fe4c1e74da88e22f6a5429dbed174b126503f8194dd32" } } ], "extra": [ 1, 209, 135, 120, 121, 198, 240, 199, 249, 165, 216, 121, 132, 117, 10, 41, 104, 98, 82, 223, 111, 64, 76, 229, 198, 218, 122, 61, 137, 16, 66, 193, 57, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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