Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e4a48360eeb160ac4e3a4b5a11b1c72c9aa2de8089ddde9096e6f0e6c8dce7e

Tx prefix hash: f823ccbec61cb88ed5332832618c25b6442662cfaba0fd2d5a5c44527129062f
Tx public key: 89788b35dcf96bd199279898e8de4ebf5f592f36f2f8cf529647a24b4fd8e188
Timestamp: 1705874805 Timestamp [UCT]: 2024-01-21 22:06:45 Age [y:d:h:m:s]: 01:261:13:15:02
Block: 940415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445708 RingCT/type: yes/0
Extra: 0189788b35dcf96bd199279898e8de4ebf5f592f36f2f8cf529647a24b4fd8e18802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96e1fedce5d695b62a2a13c5c376e4b0f27bd0dacbc71968757838ff12f70e6c 0.600000000000 1398551 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": 940425, "vin": [ { "gen": { "height": 940415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96e1fedce5d695b62a2a13c5c376e4b0f27bd0dacbc71968757838ff12f70e6c" } } ], "extra": [ 1, 137, 120, 139, 53, 220, 249, 107, 209, 153, 39, 152, 152, 232, 222, 78, 191, 95, 89, 47, 54, 242, 248, 207, 82, 150, 71, 162, 75, 79, 216, 225, 136, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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