Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4410c924a06fcd8ab2e51c7c484cddf8305964de3748ebc9785c6b8e5164d6d

Tx prefix hash: ba8e9802a3ae47d983e7888cbd1fdf279e60c9c84ddeb7c3ad822ac46ce14163
Tx public key: b50b325360d26dcc2a264717c596eb6f2fa35ebf0faed0a3963c1f0a9189b355
Timestamp: 1673043126 Timestamp [UCT]: 2023-01-06 22:12:06 Age [y:d:h:m:s]: 01:330:10:38:38
Block: 669110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497198 RingCT/type: yes/0
Extra: 01b50b325360d26dcc2a264717c596eb6f2fa35ebf0faed0a3963c1f0a9189b35502110000000352542ceb000000000000000000

1 output(s) for total of 3.723580676000 dcy

stealth address amount amount idx
00: 2bcc3a4517092c7c8078cb3eca60ae99af8a01f2d5239f4df33acae3d2e3eb2b 3.723580676000 1110411 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": 669120, "vin": [ { "gen": { "height": 669110 } } ], "vout": [ { "amount": 3723580676, "target": { "key": "2bcc3a4517092c7c8078cb3eca60ae99af8a01f2d5239f4df33acae3d2e3eb2b" } } ], "extra": [ 1, 181, 11, 50, 83, 96, 210, 109, 204, 42, 38, 71, 23, 197, 150, 235, 111, 47, 163, 94, 191, 15, 174, 208, 163, 150, 60, 31, 10, 145, 137, 179, 85, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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