Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3c263a44143a2e71f606952c7639c1efd99e50759409bbaeb95ae269b20ab73

Tx prefix hash: 121758dd6d8b4e9e2d367fca0ccbab8f8b0270a2c650780809970330887a0781
Tx public key: e403b7cb5af263578ba97fedb0a6d9d9cf6e3b2647aaed27fc623231ffb3804a
Timestamp: 1711385575 Timestamp [UCT]: 2024-03-25 16:52:55 Age [y:d:h:m:s]: 01:052:12:38:55
Block: 986163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298510 RingCT/type: yes/0
Extra: 01e403b7cb5af263578ba97fedb0a6d9d9cf6e3b2647aaed27fc623231ffb3804a02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad9f290cc4ca5117856b2ef9772480df41eb72a6a60d025322cb83fed84f07c9 0.600000000000 1446390 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": 986173, "vin": [ { "gen": { "height": 986163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad9f290cc4ca5117856b2ef9772480df41eb72a6a60d025322cb83fed84f07c9" } } ], "extra": [ 1, 228, 3, 183, 203, 90, 242, 99, 87, 139, 169, 127, 237, 176, 166, 217, 217, 207, 110, 59, 38, 71, 170, 237, 39, 252, 98, 50, 49, 255, 179, 128, 74, 2, 17, 0, 0, 0, 7, 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