Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f5926ba0ca0ae29a9aac5a463a899b4151706e615021b56103ae75d4a11565c

Tx prefix hash: 5ddc9c00895d35bf66bff6b2e9d3caf7942625e69891bba68e0fbbc4348ba856
Tx public key: 5041e119d4f7b0d984b1701a67f6ed2fe90326a6cd0451996ae87d9fa72de524
Timestamp: 1750439228 Timestamp [UCT]: 2025-06-20 17:07:08 Age [y:d:h:m:s]: 00:152:15:11:55
Block: 1309186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106928 RingCT/type: yes/0
Extra: 015041e119d4f7b0d984b1701a67f6ed2fe90326a6cd0451996ae87d9fa72de524021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41fcebf8c28cba79ac8685606b63518ca7e9215d3063f75cf88fd6f439bc650c 0.600000000000 1796801 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": 1309196, "vin": [ { "gen": { "height": 1309186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41fcebf8c28cba79ac8685606b63518ca7e9215d3063f75cf88fd6f439bc650c" } } ], "extra": [ 1, 80, 65, 225, 25, 212, 247, 176, 217, 132, 177, 112, 26, 103, 246, 237, 47, 233, 3, 38, 166, 205, 4, 81, 153, 106, 232, 125, 159, 167, 45, 229, 36, 2, 17, 0, 0, 0, 2, 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