Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f86841c3ab5aa2d8e79d9e52e93b9f487ff186938a50ee10bf166c85de1d29ef

Tx prefix hash: 8c761e0e670489f2db01cf2f6ec4cb8ba4e1bfb4441067786f2bde3445943ec1
Tx public key: 3652f1efe73749103e481dc4403773e6d1b7ae153aa14eaeadceef4859efe215
Timestamp: 1708826487 Timestamp [UCT]: 2024-02-25 02:01:27 Age [y:d:h:m:s]: 00:347:04:39:59
Block: 964927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248247 RingCT/type: yes/0
Extra: 013652f1efe73749103e481dc4403773e6d1b7ae153aa14eaeadceef4859efe2150211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb055e2c84cafce7c3e6006b67f71a23c45ee1f14c9129cbc9ab3553104c4059 0.600000000000 1424670 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": 964937, "vin": [ { "gen": { "height": 964927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb055e2c84cafce7c3e6006b67f71a23c45ee1f14c9129cbc9ab3553104c4059" } } ], "extra": [ 1, 54, 82, 241, 239, 231, 55, 73, 16, 62, 72, 29, 196, 64, 55, 115, 230, 209, 183, 174, 21, 58, 161, 78, 174, 173, 206, 239, 72, 89, 239, 226, 21, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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