Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88529b3607eaa412a8a2b877d8e9dff0967c3fbecc3be3bd55022ceffceb1261

Tx prefix hash: 00a7131bf9441add62a2eb53b6a5190b2dfdd9b7713733fc0cb74e5328f0f82c
Tx public key: 094ab5f1df181855120597729c6e65a7f0ffc9d574789c8b8468d8f232a571be
Timestamp: 1735890586 Timestamp [UCT]: 2025-01-03 07:49:46 Age [y:d:h:m:s]: 00:167:04:29:14
Block: 1189186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119152 RingCT/type: yes/0
Extra: 01094ab5f1df181855120597729c6e65a7f0ffc9d574789c8b8468d8f232a571be021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfdb5affa4df3a0ad19f6b61bf16f2ef570529903ec77a89676b32d3f8f38370 0.600000000000 1675691 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": 1189196, "vin": [ { "gen": { "height": 1189186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfdb5affa4df3a0ad19f6b61bf16f2ef570529903ec77a89676b32d3f8f38370" } } ], "extra": [ 1, 9, 74, 181, 241, 223, 24, 24, 85, 18, 5, 151, 114, 156, 110, 101, 167, 240, 255, 201, 213, 116, 120, 156, 139, 132, 104, 216, 242, 50, 165, 113, 190, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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