Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a788b26da923d1084f9dc7f2929619287efcc0081c5f9e6aa6ffc2007775df0

Tx prefix hash: 4e0a6b51e6864691a0a2123c981d4a370a42be28c628c422aa51a27c9377d0f6
Tx public key: 2590965ec9c7acf43a7c85fc7ee5d49bc4ddd8f285b2136019e10412f6659d4e
Timestamp: 1750267563 Timestamp [UCT]: 2025-06-18 17:26:03 Age [y:d:h:m:s]: 00:155:14:19:21
Block: 1307798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109002 RingCT/type: yes/0
Extra: 012590965ec9c7acf43a7c85fc7ee5d49bc4ddd8f285b2136019e10412f6659d4e021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82afaae6a178216cf2fb00d06133ae269839427619ce6e88c1caada71ff4a42f 0.600000000000 1795409 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": 1307808, "vin": [ { "gen": { "height": 1307798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82afaae6a178216cf2fb00d06133ae269839427619ce6e88c1caada71ff4a42f" } } ], "extra": [ 1, 37, 144, 150, 94, 201, 199, 172, 244, 58, 124, 133, 252, 126, 229, 212, 155, 196, 221, 216, 242, 133, 178, 19, 96, 25, 225, 4, 18, 246, 101, 157, 78, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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