Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb5df4ef1e348e9261553f9fd63a94b7fc1f7295e65dd6a53279b24cc8d561e7

Tx prefix hash: 57de5e2e1639f2654215dcf2ecc4ff028b2ae554dbfb1a8c57422970803d7507
Tx public key: a51f494e861e673ad9eeeb6737e30af6aa9251e5fb3541b360c81028a1bab9ac
Timestamp: 1758889529 Timestamp [UCT]: 2025-09-26 12:25:29 Age [y:d:h:m:s]: 00:101:11:19:51
Block: 1376868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72666 RingCT/type: yes/0
Extra: 01a51f494e861e673ad9eeeb6737e30af6aa9251e5fb3541b360c81028a1bab9ac021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3e1f1025fe0c91cc0289e68c3c4a73a95e48d184e4f16622891551b8c92f905 0.600000000000 1864959 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": 1376878, "vin": [ { "gen": { "height": 1376868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3e1f1025fe0c91cc0289e68c3c4a73a95e48d184e4f16622891551b8c92f905" } } ], "extra": [ 1, 165, 31, 73, 78, 134, 30, 103, 58, 217, 238, 235, 103, 55, 227, 10, 246, 170, 146, 81, 229, 251, 53, 65, 179, 96, 200, 16, 40, 161, 186, 185, 172, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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