Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36724d6fe1e5d228fd19cebd8a7fd481c87e8e512dbce0de49487c9c682ed9b6

Tx prefix hash: 2c344fc713c82368e2ac6b3aa2a752fc40dc8eef97524ec865849bea8e4b8c58
Tx public key: f652f67a37fc89f329d305eafaa7eacd7fb9b7b53d5af426ccbab76e5594c346
Timestamp: 1746996088 Timestamp [UCT]: 2025-05-11 20:41:28 Age [y:d:h:m:s]: 00:186:11:03:37
Block: 1280838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130971 RingCT/type: yes/0
Extra: 01f652f67a37fc89f329d305eafaa7eacd7fb9b7b53d5af426ccbab76e5594c3460211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 507dd0991cf56afcd08eb887dfaeb67b8a72fde3eaf36e32370e80b70381e7f3 0.600000000000 1768231 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": 1280848, "vin": [ { "gen": { "height": 1280838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "507dd0991cf56afcd08eb887dfaeb67b8a72fde3eaf36e32370e80b70381e7f3" } } ], "extra": [ 1, 246, 82, 246, 122, 55, 252, 137, 243, 41, 211, 5, 234, 250, 167, 234, 205, 127, 185, 183, 181, 61, 90, 244, 38, 204, 186, 183, 110, 85, 148, 195, 70, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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