Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e59554da1be3e002bfbab73f51f502f6281daa9e80d47cb423f44a010b17c46

Tx prefix hash: ccab59aa18cf3dd86a73950802318a32cac92348309651678d0f009e5f9e84ab
Tx public key: fb20d8e717f9892558260c596e964aeba0bf277f4840a052ba15ecc2cbf86a02
Timestamp: 1744613748 Timestamp [UCT]: 2025-04-14 06:55:48 Age [y:d:h:m:s]: 00:221:00:48:46
Block: 1261126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155673 RingCT/type: yes/0
Extra: 01fb20d8e717f9892558260c596e964aeba0bf277f4840a052ba15ecc2cbf86a020211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee1cf8a0df591f60a9a5027af632636c025a922bca9d2aae2afdc933f7319428 0.600000000000 1748291 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": 1261136, "vin": [ { "gen": { "height": 1261126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee1cf8a0df591f60a9a5027af632636c025a922bca9d2aae2afdc933f7319428" } } ], "extra": [ 1, 251, 32, 216, 231, 23, 249, 137, 37, 88, 38, 12, 89, 110, 150, 74, 235, 160, 191, 39, 127, 72, 64, 160, 82, 186, 21, 236, 194, 203, 248, 106, 2, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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