Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5eceb46861808060c3cd48c39149c523aa923fbfb2aa4ab25935c0e56b1620ae

Tx prefix hash: 9e822d347f8df7f44ed63816a0a6c454496b1826e6817fbe2bee0d8578028da0
Tx public key: 51609d78866229e887026c1dd6023b996a53a1f93a512203682658462a7e34a1
Timestamp: 1672807838 Timestamp [UCT]: 2023-01-04 04:50:38 Age [y:d:h:m:s]: 02:093:06:27:55
Block: 667178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588339 RingCT/type: yes/0
Extra: 0151609d78866229e887026c1dd6023b996a53a1f93a512203682658462a7e34a102110000000133af99f4000000000000000000

1 output(s) for total of 3.778872932000 dcy

stealth address amount amount idx
00: 7a085dd32bce70c905ec8a5e0d44c6321a2d333b2bdb674f0a1b01224a3fdbc1 3.778872932000 1108343 of 0

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": 667188, "vin": [ { "gen": { "height": 667178 } } ], "vout": [ { "amount": 3778872932, "target": { "key": "7a085dd32bce70c905ec8a5e0d44c6321a2d333b2bdb674f0a1b01224a3fdbc1" } } ], "extra": [ 1, 81, 96, 157, 120, 134, 98, 41, 232, 135, 2, 108, 29, 214, 2, 59, 153, 106, 83, 161, 249, 58, 81, 34, 3, 104, 38, 88, 70, 42, 126, 52, 161, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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