Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 509afaeccb514deb36d50a3b2ef81e4fc03e22b829b2ded8cd8a91dafc043655

Tx prefix hash: 8ff9f83789ca7d02c52624532d2e579b5da8725d89fad81c4d90adb8bb4be909
Tx public key: 5b81b68007a83439e250c97c619e20697cb34c2554aec5fa1a5c296ef5f3523c
Timestamp: 1755703210 Timestamp [UCT]: 2025-08-20 15:20:10 Age [y:d:h:m:s]: 00:060:04:12:02
Block: 1350659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42897 RingCT/type: yes/0
Extra: 015b81b68007a83439e250c97c619e20697cb34c2554aec5fa1a5c296ef5f3523c021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6087f9da2cbab7b68b6f24eb1a1e73b73e67f8cc4a944d2972c766702022c903 0.600000000000 1838604 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": 1350669, "vin": [ { "gen": { "height": 1350659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6087f9da2cbab7b68b6f24eb1a1e73b73e67f8cc4a944d2972c766702022c903" } } ], "extra": [ 1, 91, 129, 182, 128, 7, 168, 52, 57, 226, 80, 201, 124, 97, 158, 32, 105, 124, 179, 76, 37, 84, 174, 197, 250, 26, 92, 41, 110, 245, 243, 82, 60, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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